From 428c7845fff307f0f90c8aa6e181274a28da0f58 Mon Sep 17 00:00:00 2001 From: Jose Borreguero Date: Fri, 5 Aug 2022 20:57:51 -0400 Subject: [PATCH] polish the devops guide Signed-off-by: Jose Borreguero --- docs/developer/devops/index.rst | 25 ++++++------------------- 1 file changed, 6 insertions(+), 19 deletions(-) diff --git a/docs/developer/devops/index.rst b/docs/developer/devops/index.rst index a8168e2..a49d207 100644 --- a/docs/developer/devops/index.rst +++ b/docs/developer/devops/index.rst @@ -32,27 +32,14 @@ Deployment for Testing ---------------------- Deployment for the testing environment is handled by the -[web relectivity deploy repo](https://code.ornl.gov/sns-hfir-scse/deployments/web-reflectivity-deploy). -The `deploy` stage in `.gitlab-ci.yml` will trigger the web reflectivity -deploy repo to run its version of `docker-compose.yml` to deploy the app -to the testing environment. +`web-relectivity-deploy repo `_. +For details on how to deploy, read the +`Guide for the deployment to Testing Environment `_. + Deployment in Production ------------------------ This deployment is scheduled to happen after a new version of the software is released and thoroughly tested in deployment `testenv`. - -Topics still undefined -====================== -- does the deployment to production should be manual or automated - (i.e. automatically triggered when a new version is tagged)? -- How to preserve the database in the production environment? - Options are: - - + prevent the database container from stopping. This requires deployment - of all services except the database, and then connecting the container - running those services to the container running the database. - This option poses a problem when the new release aims to actualize - the database software! - + :ref:`dump the database` into a file, then deploy - the new release, then upload the dump file into the database container. +For details on how to deploy, read the +`Guide for the deployment to Production Environment `_. -- GitLab