From 6a69b347363924e67dfdbb842c0f7b07146264b6 Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Tue, 24 Dec 2019 18:55:40 +0000 Subject: [PATCH] --- devdocs/deploy.txt | 2 +- devdocs/todo.txt | 2 ++ 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/devdocs/deploy.txt b/devdocs/deploy.txt index 7026e385..9243262c 100644 --- a/devdocs/deploy.txt +++ b/devdocs/deploy.txt @@ -57,7 +57,7 @@ BUILD SERVER - ERASE DB, FETCH LICENSE, GENERATE DATA - ERASE DB: - Stop container if not already stopped: execute sudo docker-compose down - - Edit docker-compose.yml, uncomment line with erase db environment variable and re-start to erase db + - Edit nano docker-compose.yml, uncomment line with erase db environment variable and re-start to erase db - sudo docker-compose up -d - Stop the container again, use nano to edit docker-compose.yml and re-comment the erase db environment variable - Start the container again with the up command diff --git a/devdocs/todo.txt b/devdocs/todo.txt index f801b816..f6506c99 100644 --- a/devdocs/todo.txt +++ b/devdocs/todo.txt @@ -33,6 +33,8 @@ TODO: "Service workorders" now "workorders" do for non english locales, keys cha TODO: DO I NOT HAVE AN ERASE DB ROUTE? - wouldn't that make the below possible?? +TODO: Is there a log that records past jobs + TODO: NEEDS A THINK, SOME CHANGES REQUIRE DB ERASURE BEFORE STARTUP - Make it fucking easier to test deploy and erase db and fetch key and all that shit - How about one click to erase the db, fetch the trial key and seed the data???