ayanova/devdocs/todo.txt

@@ -24,7 +24,6 @@ Prioritize anything that stands in the way of beta testing
 
 
 TODO: 
-testing cases
 #1 issues below in list
 docs cleanup
 features in immediate block below 
@@ -148,19 +147,9 @@ Coded by importance
 
 - 1 todo: update the version of postgreSQL in the "single" standalone installer (but do it for myself first in my dev standalone pg server)
 
-- 1 todo (may be done already I think?): 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 physical file??
-		This way it can properly write out whatever paths necessary in single installer at least
-
-- 1 todo: ideally installer should have a commented out jwt secret that wont' take effect but has text like "EDITME AND UNCOMMENT" or whatever
 
 
-
-- 2 todo: test single liner upgrade command in linux:
-	sudo systemctl stop ayanova.service && rm *.dll && rm -r ./resource && rm -r ./wwwroot && unzip -o ayanova-linux-x64-server.zip -x "config.json" && sudo systemctl start ayanova.service
-
+- 2 todo: ideally installer should have a commented out jwt secret that wont' take effect but has text like "EDITME AND UNCOMMENT" or whatever
 - 2 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
 	Github watch and star all tools used for starters so get notifications via github about new releases etc
@@ -179,11 +168,6 @@ Coded by importance
 ╚═════╝  ╚═════╝  ╚═════╝ ╚═════╝ ╚═╝     ╚═╝╚══════╝╚═╝  ╚═══╝   ╚═╝   ╚═╝  ╚═╝   ╚═╝   ╚═╝ ╚═════╝ ╚═╝  ╚═══╝
 
 
-TODO: 1 DOCS MUST BE VERSIONED
-	put the release version into the index page of docs prominently e.g. "Version 8.0.0-beta.0.9"
-	This is because when code changes docs often will change and they must be matched so this is a way to check that
-
-TODO: Hardware requirements should be 2gb minimum due to printing, 1gb would work if not printing a large load
 
 TODO: 1 BETA DOCS:
 	- *** IMPORTANT *** before beta go through *every* doc page one at a time and read through them for outdated stuff and wording that should not be public
@@ -223,8 +207,7 @@ TODO: 1 BETA DOCS:
 ██  ██  ██ ██ ██    ██ ██   ██ ██   ██    ██    ██      
 ██      ██ ██  ██████  ██   ██ ██   ██    ██    ███████ 
                                                         
-- 1: change the installer to be named v8-migrate.exe and publish it to the new download/ folder instead
-	also update the version number to match the release, since it likely won't change much maybe just make it 8.0.0-beta.1 directly
+
 
 
 ## TESTING ITEMS
@@ -280,18 +263,19 @@ TODO: 1 BETA DOCS:
 	is required to troubleshoot failed install
 - 1 bugbug?:open vendor, print report, go back it shows as savable all of a sudden despite no changes made in UI, also does not give dirty save prompt when leave it even though save icon is showing enabled bold
 - 1 fixed?? changed to attachment files path : for some reason user files path is blank in server settings under ops in ayanova app on linux desktop when using the single data path folder, check in windows
-- 1 todo: First print if it's downloading or will need to download chromium it should state there will be a delay while it attempts to download and install chromium render engine
-	or maybe trigger it on first boot?
+
 - 1 todo: firefox schedule fix: https://github.com/vuetifyjs/vuetify/issues/14243#issuecomment-944907925
 	this should fix on it's own with an update to vuetify which was just patched 2021-11-09 and not released yet
 
 - 1 translation cleanup, work order sb Orden de trabajo but is translated as Pedido?! (which is very generic and not work order, usually like a restaurant order or online shipping order sense for pedido)
 	I did a couple but realized it needs to be done one by one roundtripped carefully as it's used in alternative tenses and forms throughout
 
+
+
+- 2 todo: First print if it's downloading or will need to download chromium it should state there will be a delay while it attempts to download and install chromium render engine
+	or maybe trigger it on first boot?
 -2 ops server information is missing some settings like report rendering max instances, go over the serverbootconfig settings and look for missing items to add
 
-
-
 -2 Schedule, what is the maximum number of techs can show in team view, can show more with scroll?
 	seeder should prevent going over this max (tags/prefilter/gen less)