This commit is contained in:
@@ -150,7 +150,8 @@ Coded by importance
|
||||
- 1 todo: apparently it's easy to pick an alternate folder for install in windows single and it fucks with postgres path so not sure what to do with that
|
||||
maybe force the default installation location for windows single only so people don't fuck it up?
|
||||
Or add a warning we *STRONGLY advise not changing the default location or you will need to change config.json
|
||||
or, is it possible to write out the config.json from the installer and not include it as a file??
|
||||
or, is it possible to write out the config.json from the installer and not include it as a physical file??
|
||||
This way it can properly write out whatever paths necessary in single installer at least
|
||||
|
||||
- 1 todo: subscribe to all sources of security vulnerabilities that could apply to users of AyaNOva 8 (and 7)
|
||||
Need an ongoing defined process to follow to ensure we are not caught by surprise with any security vulnerabilities
|
||||
@@ -418,6 +419,9 @@ todo: 3 Schedule form reporting?
|
||||
|
||||
- 1 todo: update all back end dependencies
|
||||
|
||||
todo: 1 VERY IMPORTANT test on windows where all paths have spaces, i.e. set the server data path to a location with funky folder names with spaces etc
|
||||
confirm everything in raven that writes to disk still works, logging, backup, attachments, temp files served (reports) etc
|
||||
|
||||
TODO: 1 Log the startup folder for AyaNova and provide in all areas where you can view config because user may have trouble locating it on windows
|
||||
|
||||
todo: 2 lost contact with db server notification message to be sent once to ops admin??
|
||||
|
||||
Reference in New Issue
Block a user