This commit is contained in:
@@ -5,21 +5,6 @@ choco upgrade chocolatey
|
||||
todo: ip address logged in container mode is the local server as I guess it comes from NGINX
|
||||
is there a way to capture this or...?
|
||||
|
||||
todo: AYANOVA_SERVER_TEST_MODE Is this a thing anymore? I think I need to remove it as an environment variable and all the startup code to go with it
|
||||
todo: AYANOVA_PERMANENTLY_ERASE_DATABASE does more than that, also resets dbid, should this option name be changed to something more dire
|
||||
it sounds just like the option in ayaNova to erase all data but those are two different things
|
||||
"permanently" is redundant as well.
|
||||
todo: permanently erase db startup thing, should it really exist?
|
||||
It will zap the dbid so a user might expect to just use their old license but it wont' fetch again
|
||||
we could issue a new key to replace with the new dbid and also issue a revoke key for the old dbid so that
|
||||
there can be no fraudulent use this way.
|
||||
I guess it's a rare situation and if the option to delete is there people will surely fuck up and use it unintentionally?
|
||||
or maybe not
|
||||
todo: could be a presentation issue but erasing the database and "permanently" erasing the db do two different things completely
|
||||
Maybe change the biz object erase to empty or remove all data or something along those lines
|
||||
If it requires too much explanation then it's probably mis-identified as to what it does
|
||||
|
||||
|
||||
todo: docs, change all named references to the Manager / manager / admin / adminstrator account to "SuperUser"
|
||||
|
||||
todo: add alternate, backup domain to be checked for license key if primary can't be reached
|
||||
|
||||
Reference in New Issue
Block a user