Changes

Page history
Update Simplified_Deployment authored by Jacob Benz's avatar Jacob Benz
Show whitespace changes
Inline Side-by-side
Simplified_Deployment.md
View page @ 09defaec
...@@ -37,9 +37,9 @@ From time to time it may be desirable to update LEAF-Writer and its dependencies ...@@ -37,9 +37,9 @@ From time to time it may be desirable to update LEAF-Writer and its dependencies
To update LEAF-Writer and its components do the following: To update LEAF-Writer and its components do the following:
1. Connect to your server and navigate to the directory with the cloned LEAF-Writer source. 1. Connect to your server and navigate to the directory with the cloned LEAF-Writer source.
2. Stop and remove the containers of the currently running LEAF-Writer version with `sudo docker compose --env-file leafwriter.env -f docker-compose.yml down` 2. Stop and remove the containers of the currently running LEAF-Writer version with `sudo docker compose --env-file leafwriter.env -f docker-compose.yml down`
3. Update the LEAF-Writer repository with all its submodules: `git submodule update --recursive` 3. Pull & Update the LEAF-Writer repository with all its submodules: `git pull && git submodule update --recursive`
4. Update all locally build containers: `sudo docker compose --env-file leafwriter.env -f docker-compose.yml build --no-cache --pull` 4. Update all locally build containers: `sudo docker compose --env-file leafwriter.env -f docker-compose.yml build --no-cache --pull`
5. Start LEAF-Writer again and force a pull from the registry for all containers that are not locally build: `sudo docker compose --env-file leafwriter.env -f docker-compose.yml up --build --pull always`. You can add the `-d` flag if you feel brave and want to start everything directly in background. Otherwise it may be a good idea to first check the outputs, then stop the containers with `Ctrl+c`, run `sudo docker compose --env-file leafwriter.env -f docker-compose.yml down` and as the last step, if the output logs where fine and LEAF-Writer was reachable and worked reasonably well, start everything in detached mode with ``sudo docker compose --env-file leafwriter.env -f docker-compose.yml up -d` 5. Start LEAF-Writer again and force a pull from the registry for all containers that are not locally build: `sudo docker compose --env-file leafwriter.env -f docker-compose.yml up --build --pull always`. You can add the `-d` flag if you feel brave and want to start everything directly in background. Otherwise it may be a good idea to first check the outputs, then stop the containers with `Ctrl+c`, run `sudo docker compose --env-file leafwriter.env -f docker-compose.yml down` and as the last step, if the output logs where fine and LEAF-Writer was reachable and worked reasonably well, start everything in detached mode with `sudo docker compose --env-file leafwriter.env -f docker-compose.yml up -d`
**Note**: **Note**:
... ...
......