3
3
4
4
# docker compose stacks for wger
5
5
6
- The prod docker compose file starts up a production environment with the application
7
- server, a reverse proxy, a database, a caching server and a celery queue all
8
- configured.
6
+ The production Docker Compose file initializes a production environment with the
7
+ application server, a reverse proxy, a database, a caching server, and a Celery
8
+ queue, all configured. Data is persisted in volumes, if you want to use folders,
9
+ read the warning in the env file.
9
10
10
- Basically, just do ` docker compose up -d ` . For more details, consult the documentation:
11
+ ** TLDR: ** just do ` docker compose up -d `
11
12
12
- * prod: < https://wger.readthedocs.io/en/latest/production/docker.html >
13
- * dev: < https://wger.readthedocs.io/en/latest/development/docker.html >
13
+ For more details, consult the documentation (and the config files):
14
+
15
+ * production: < https://wger.readthedocs.io/en/latest/production/docker.html >
16
+ * development: < https://wger.readthedocs.io/en/latest/development/docker.html >
17
+
18
+ It is recommended to regularly pull the latest version of the compose file,
19
+ since sometimes new configurations or environmental variables are added.
14
20
15
21
## Contact
16
22
@@ -19,9 +25,9 @@ didn't behave as you expected. We can't fix what we don't know about, so please
19
25
report liberally. If you're not sure if something is a bug or not, feel free to
20
26
file a bug anyway.
21
27
22
- * discord : < https://discord.gg/rPWFv6W >
23
- * issue tracker : < https://github.com/wger-project/docker/issues >
24
- * twitter : < https://twitter .com/wger_project >
28
+ * Mastodon : < https://fosstodon.org/@wger >
29
+ * Discord : < https://discord.gg/rPWFv6W >
30
+ * Issue tracker : < https://github .com/wger-project/docker/issues >
25
31
26
32
27
33
## Sources
0 commit comments