Skip to content

Commit 413b8a8

Browse files
authored
Merge pull request #97 from ccdc-opensource/stack-restart-commands
NO_JIRA correct stack restart commands
2 parents d243869 + 6a34629 commit 413b8a8

1 file changed

Lines changed: 16 additions & 8 deletions

File tree

README.md

Lines changed: 16 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -241,12 +241,22 @@ docker compose ps
241241
```
242242

243243
which should show the state of the services to all be `Up`. If any services have the state `Up (unhealthy)` or `Exit` then restart the stack.
244-
Take care to include the right config files as in the commands below.
244+
In most cases it is best to leave the postgres server running as in the commands below.
245245

246246
```sh
247247
# Include docker-compose.insecure-configuration.yml if using a self-signed certificate
248-
# Omit docker-compose.postgres.yml if self-hosting your postgres server
248+
docker compose -f docker-compose.yml -f docker-compose.ssl.yml down
249+
docker compose -f docker-compose.yml -f docker-compose.ssl.yml up -d
250+
```
251+
252+
If the csd-database container is unhealthy then do a full restart of the stack and bring it up before the other containers.
253+
254+
```sh
255+
# Follow the above instructions instead if using a self-hosted postgres server
256+
# Include docker-compose.insecure-configuration.yml if using a self-signed certificate
249257
docker compose -f docker-compose.yml -f docker-compose.ssl.yml -f docker-compose.postgres.yml down
258+
259+
docker compose -f docker-compose.yml -f docker-compose.ssl.yml -f docker-compose.postgres.yml up -d csd-database
250260
docker compose -f docker-compose.yml -f docker-compose.ssl.yml -f docker-compose.postgres.yml up -d
251261
```
252262

@@ -325,10 +335,9 @@ To change your license key you must delete the license volume and restart the st
325335

326336
```sh
327337
# Include docker-compose.insecure-configuration.yml if using a self-signed certificate
328-
# Omit docker-compose.postgres.yml if self-hosting your postgres server
329-
docker compose -f docker-compose.yml -f docker-compose.ssl.yml -f docker-compose.postgres.yml down
338+
docker compose -f docker-compose.yml -f docker-compose.ssl.yml down
330339
rm -r lic
331-
docker compose -f docker-compose.yml -f docker-compose.ssl.yml -f docker-compose.postgres.yml up -d
340+
docker compose -f docker-compose.yml -f docker-compose.ssl.yml up -d
332341
```
333342

334343
## Updates
@@ -354,10 +363,9 @@ For major releases export any in-house databases, recreate the csd-database and
354363

355364
```sh
356365
# Include docker-compose.insecure-configuration.yml if using a self-signed certificate
357-
# Omit docker-compose.postgres.yml if self-hosting your postgres server
358-
docker compose -f docker-compose.yml -f docker-compose.ssl.yml -f docker-compose.postgres.yml down
366+
docker compose -f docker-compose.yml -f docker-compose.ssl.yml down
359367
docker compose pull
360-
docker compose -f docker-compose.yml -f docker-compose.ssl.yml -f docker-compose.postgres.yml up -d
368+
docker compose -f docker-compose.yml -f docker-compose.ssl.yml up -d
361369
```
362370

363371
Now from lattice -> database management, reimport your in-house databases.

0 commit comments

Comments
 (0)