admin/raven
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Browse Source
This commit is contained in:
John Cardinal
2018-10-11 21:37:05 +00:00
parent 5e6a042dcf
commit 9de3924286
5 changed files with 56 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
devdocs/todo.txt
View File

@@ -39,7 +39,7 @@ IMMEDIATE ITEMS:
- Seeder should be changed to log job info for each step
- Should server show uptime?
- Log route: Add a route to download *all* log files as a single zip archive which will make life much easier for analysis

13
devdocs/tools.txt
View File

@@ -92,9 +92,9 @@ https://risingstars.js.org/2017/en/
- Run new image
- sudo docker-compose up -d
- Restart NGINX container as it seems to lose it's mind when the AyaNova container is restarted (502 BAD GATEWAY error)
- from /docker/letsencrypt-docker-nginx/src/production run sudo docker-compose up -d
- Or just use the restartnginx.sh script in xfer at the server
- Restart NGINX container (IF NECESSARY) as it seems to sometimes lose it's mind when the AyaNova container is restarted (502 BAD GATEWAY error)
- use the restartnginx.sh script in xfer at the server
- or from /docker/letsencrypt-docker-nginx/src/production run sudo docker-compose up -d
- Test
- If 502 BAD GATEWAY then AyaNova server is not up so the NGINX config bombs because it's proxying to it.
@@ -107,10 +107,13 @@ https://risingstars.js.org/2017/en/
- 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
- sudo docker-compose up -d
- Stop the container again, use nano to edit docker-compose.yml and re-comment the erase db evenironment variable
- 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
- FETCH TEST KEY:
- Go into the api explorer, authenticate then select the POST to license route (not the TRIAL one), this will fetch a test key and install it
- Go into the api explorer, authenticate then
- select the POST to license Trial route first { "registeredTo": "TestCo", "emailAddress": "cardjohn@ayanova.com"}
- This seems to setup the db to accept a trial key when fetching the regular key next
- select the POST to license route (not the TRIAL one), this will fetch a test key and install it
- SEED DB:
- Go to trial route and pick seed level (HUGE for proper testing) and activate
- NOTE: as of today 2018-10-9 it takes 8 minutes at the Devops server to generate the HUGE dataset