Skip to Content

Changes for page Software Stacks

Last modified by chrisby on 2024/08/29 14:47
From version 1.6
edited by chrisby
on 2023/09/09 16:37
Change comment: There is no comment for this version
To version 1.7
edited by chrisby
on 2023/09/09 16:39
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -8,7 +8,7 @@
8 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 merge the service configuration from one {{code language="none"}}docker-compose.yml{{/code}} into another.
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 {{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.
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 the {{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 or real certificates for new stacks, just shut down Traefik, delete its volume and restart it.
12 12  
13 13  (% style="text-align: justify;" %)
14 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.