This commit is contained in:
@@ -13,7 +13,8 @@ https://medium.com/@wesharehoodies/immensely-upgrade-your-development-environmen
|
||||
Changes needed to routes??
|
||||
- http://www.talkingdotnet.com/actionresult-t-asp-net-core-2-1/
|
||||
|
||||
|
||||
Ensure all modern best practice security is properly enabled on helloayanova.com so testing is valid
|
||||
- https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security#Deployment_best_practices
|
||||
|
||||
CODING WORK
|
||||
+++++++++++
|
||||
@@ -28,17 +29,14 @@ Once that is done then can steam ahead on the biz objects but until I have the c
|
||||
IMMEDIATE ITEMS:
|
||||
================
|
||||
|
||||
|
||||
- LOGIN logging, seems like too much, maybe drop it down a level into a diagnostic level? Or an option to be turned on?
|
||||
THIS: 2018-10-04 11:50:29.8943|INFO|AyaNova.Api.Controllers.AuthController|User number "7" logged in from "::ffff:127.0.0.xxx" ok
|
||||
|
||||
- Before moving on with api completely: Create a batch file to run integration tests in a loop and make it run overnight to see what shakes out at the server in terms of errors etc.
|
||||
|
||||
Ensure all modern best practice security is properly enabled on helloayanova.com so testing is valid
|
||||
- https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security#Deployment_best_practices
|
||||
- Seeder.SeedDatabase should accept a JobId parameter so it can log each step in the job if present
|
||||
-TrialBiz line 73 calls it and should be changed to pass the JobId
|
||||
- Seeder should be changed to log job info for each step
|
||||
|
||||
- Put up copy to devops, build huge dataset, run all tests
|
||||
|
||||
- Should server show uptime?
|
||||
|
||||
************************************************************************************
|
||||
FUTURE ITEMS:
|
||||
=============
|
||||
|
||||
@@ -102,7 +102,17 @@ https://risingstars.js.org/2017/en/
|
||||
- Check logs with sudo docker logs [containerID] to find out what happened
|
||||
- Or in some cases (once) Digital Ocean fucked up something
|
||||
|
||||
|
||||
- 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
|
||||
- sudo docker-compose up -d
|
||||
- Stop the container again, use nano to edit docker-compose.yml and re-comment the erase db evenironment 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
|
||||
- SEED DB:
|
||||
- Go to trial route and pick seed level (HUGE for proper testing) and activate
|
||||
|
||||
|
||||
### Publish command line:
|
||||
|
||||
Reference in New Issue
Block a user