@@ -56,23 +56,30 @@ Start by creating the `.prod.env` file (if it does not exist yet), by running:
5656cp .env.template .prod.env
5757```
5858
59- Then, edit the ` .prod.env ` file and provide values for all variables marked as required in the list of [ environment variables] ( ../environment/ ) .
59+ Then, edit the ` .prod.env ` file and provide values for all variables marked as required in the list of [ environment variables] ( ../environment/ ) .
6060
6161### Start docker containers
6262
6363Before proceeding, ensure you have both ` docker ` and ` docker-compose ` installed on your system.
6464
65- Once your environment is configured, you can start the containers by running:
65+ Once your environment is configured, you can start the containers by running the following commands for the Community and Enterprise editions.
66+
67+ Community edition stack:
68+
6669``` shell
67- # For community edition
68- $ mkdir -p mergin_db # or wherever you set it to be
69- $ sh ../common/set_permissions.sh projects
70+ $ mkdir -p mergin_db # database data directory
71+ $ sh ../common/set_permissions.sh projects # application internal data directory
72+ $ sh ../common/set_permissions.sh diagnostic_logs # directory to persist diagnostic logs (optional)
7073$ docker-compose -f docker-compose.yml up -d
74+ ```
7175
72- # For enterprise edition
73- $ mkdir -p mergin-db-enterprise # or wherever you set it to be
74- $ sh ../common/set_permissions.sh data
75- $ sh ../common/set_permissions.sh map_data
76+ Enterprise edition stack:
77+
78+ ``` shell
79+ $ mkdir -p mergin-db-enterprise # database data directory
80+ $ sh ../common/set_permissions.sh data # application internal data directory
81+ $ sh ../common/set_permissions.sh map_data # maps data directory (neccessary for maps)
82+ $ sh ../common/set_permissions.sh diagnostic_logs # directory to persist diagnostic logs (optional)
7683$ docker-compose -f docker-compose.yml up -d
7784$ docker-compose -f docker-compose.maps.yml up -d # Run maps stack separately
7885```
0 commit comments