What is your preferred way of storring and deploying docker-compose stacks?

• Nginx Proxy Manager

  651 19,499 8.8 JavaScript

  Docker container for managing Nginx proxy hosts with a simple, powerful interface

  

So i'm hoping soon to spend some time with https://nginxproxymanager.com/ and get the same feature set.

• Code-Server

  395 65,172 9.2 TypeScript

  VS Code in the browser

  

I keep all my stacks in a git repository that I have mounted into a Code-Server container. Once I make modifications they get pushed to a Gitea container. From there I have the stack set up within Portainer to keep in sync with the git repository, so any changes I make to the stack like adding labels, volume mounts, or container versions are automatically pulled in by Portainer and applied to the running stack immediately once the modifications get sent to Gitea. Also I have a Renovate bot checking through this repository continuously for new versions of my container images. When it finds one, it proposes the new image in the form of a pull-request on the repository along with a changelog from the author of the container image. Once I decide to approve the changes, that again gets pulled in by Portainer and the stack is changed accordingly.

• SurveyJS

  surveyjs.io sponsored

  Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.

  

• Gitea

  280 41,708 10.0 Go

  Git with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CD

  

I keep all my stacks in a git repository that I have mounted into a Code-Server container. Once I make modifications they get pushed to a Gitea container. From there I have the stack set up within Portainer to keep in sync with the git repository, so any changes I make to the stack like adding labels, volume mounts, or container versions are automatically pulled in by Portainer and applied to the running stack immediately once the modifications get sent to Gitea. Also I have a Renovate bot checking through this repository continuously for new versions of my container images. When it finds one, it proposes the new image in the form of a pull-request on the repository along with a changelog from the author of the container image. Once I decide to approve the changes, that again gets pulled in by Portainer and the stack is changed accordingly.

• renovate

  113 15,658 10.0 TypeScript

  Universal dependency automation tool.

  

I keep all my stacks in a git repository that I have mounted into a Code-Server container. Once I make modifications they get pushed to a Gitea container. From there I have the stack set up within Portainer to keep in sync with the git repository, so any changes I make to the stack like adding labels, volume mounts, or container versions are automatically pulled in by Portainer and applied to the running stack immediately once the modifications get sent to Gitea. Also I have a Renovate bot checking through this repository continuously for new versions of my container images. When it finds one, it proposes the new image in the form of a pull-request on the repository along with a changelog from the author of the container image. Once I decide to approve the changes, that again gets pulled in by Portainer and the stack is changed accordingly.

Suggest a related project