Skip to Content

Changes for page Software Stacks

Last modified by chrisby on 2024/08/29 14:47
From version 1.3
edited by chrisby
on 2023/09/03 18:57
Change comment: There is no comment for this version
To version 1.4
edited by chrisby
on 2023/09/03 23:29
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -2,16 +2,16 @@
2 2  === Introduction ===
3 3  
4 4  (% style="text-align: justify;" %)
5 -I love open source software, especially when it can be deployed seamlessly via Docker. I often combine deployments with Traefik, which greatly simplifies the reverse proxying process and certificate generation. However, individual projects often have unique nuances and configurations. So I've created this section to show you how to deploy the software I'm working on with no more than two commands.
5 +I love open source software, especially when it can be deployed seamlessly via Docker. However, individual projects often have unique nuances and configurations. So I've created this section to show you how to deploy the software I'm working on with no more than two commands. To get a working deployment of a software stack, simply copy the {{code language="none"}}docker-compose.yml{{/code}} from the article, replace any variables with the format {{code language="none"}}<some-variable>{{/code}} with an actual value, and follow the instructions.
6 6  
7 7  (% style="text-align: justify;" %)
8 -All the configurations described in the subsections use Traefik as a reverse proxy. It's also possible to combine all the stacks below on a single device behind a single Traefik container. Just copy the service configuration in one docker-compose.yml to another docker-compose.yml and run "docker-compose up -d" to do the rest.
8 +All the configurations described in the subsections use Traefik, which greatly simplifies the reverse proxying process and certificate generation. It's also possible to combine all the stacks on a single device behind a single Traefik container. Just copy the service configuration from one {{code language="none"}}docker-compose.yml{{/code}} to another {{code language="none"}}docker-compose.yml{{/code}}.
9 9  
10 10  (% style="text-align: justify;" %)
11 -Traefik will automatically generate an appropriate LetsEncrypt certificate on startup. It's worth noting that there is currently a limit of 5 LetsEncrypt certificates per 24 hour period. However, there's an option in the Traefik settings in docker-compose.yml to manually disable this and use dummy certificates instead. This comes in handy if you're in the experimental phase and are initiating multiple deployments per day. If you want to get rid of the dummy certificates, just shut down Traefik, delete its volume and restart it.
11 +Traefik will automatically generate an appropriate LetsEncrypt certificate on startup. It's worth noting that there is currently a limit of 5 LetsEncrypt certificates per 24 hour period. However, there's an option in the Traefik settings in {{code language="none"}}docker-compose.yml{{/code}} to manually disable this and use dummy certificates instead. This comes in handy if you're in the experimental phase and are initiating multiple deployments per day. If you want to get rid of the dummy certificates, just shut down Traefik, delete its volume and restart it.
12 12  
13 13  (% style="text-align: justify;" %)
14 -In each docker-compose.yml, unambiguous docker image tags are set. The reason for this is to keep the deployment stable. Nothing is more frustrating than having bugs during deployment and having to find a working set of image versions when you just want to test the software. If you intend to use the software in production, I recommend deploying the latest version of the containers to avoid unnecessary security vulnerabilities and to get the latest features.
14 +In each {{code language="none"}}docker-compose.yml{{/code}}, unambiguous docker image tags are set. The reason for this is to keep the deployment stable. It's frustrating to encounter bugs during deployment due to outdated configurations or incompatible container versions, especially when you're just testing the software. If you intend to use the software in production, I recommend reading the documentation or experimenting with the latest version of containers to get a stable set. This will avoid unnecessary security vulnerabilities and give you the latest features.
15 15  
16 16  
17 17  (% style="text-align: justify;" %)