ayanova/devdocs/todo.txt

@@ -23,27 +23,26 @@ Prioritize anything that stands in the way of beta testing
 TODO: NEXT: 
 
 ## LINUX NGINX INSTALL 
-spin up a test server with DO so can do the whole thing from top to bottom
+Follow the new docs to setup the (h)amsterdam trial52.helloayanova.com site and confirm all steps are there or as much as needed
-or, do I just zap our test server and start from scratch again??
+Mostly for my own use etc
-I guess if I backup the nginx and any special config I can do that
 
-for 5 bucks though far easire to just fire up a new one
+## LINUX DOCKER INSTALL (umm...maybe not, see below)
-Do that first so can configure networking to point a subdomain to it for later nginx etc config (under HELLOAYANOVA.COM though, not ayanova.com!!)
-
-## LINUX DOCKER INSTALL
 Make a new docker setup and use the droplet from above wiped again to test that out
+kind of leaning against any docker setup now as it doesn't really save much time and it won't get patched / updated through normal linux means
+
 
 ## TEST BACKUP AND RESTORE USING GREEN TESTINSTALLER DROPLET FROM HERE WINDOWS BACKUP
 this is ultimate test, make sure have attachments etc, do full backup and full restore
 document it and build docs for it
 
-## FINAL BETA INSTALL TASK
+## FINAL BETA INSTALL EVERYTHING TO CONFIRM DOCS
 TODO: FInally, last step before considering installs done is to do a fresh round of all installs following docs and make sure nothing missed or unclear or not working as expected
 
 
 
 
 
+
 TODO IMMINENTLY
 - 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
 - Can't shut down the server in first boot from client due to no ops ui available, ops sb available even when not licensed possibly?
@@ -66,6 +65,7 @@ OUTSTANDING MAJOR AREAS TO BETA
 			zip installer with guidance
 	Test restore!!! Super important, also document it in manual
 	Reports (stock)	
+		mostly there but issue with ordering and missing some obvious ones like Customer etc that should have at least *something* there
 	trial / seeder system
 		do not specify by size but rather scenario
 		we care about size for load testing but don't want to give impression we think HUGE is just a few 10s of thousands of workorders because it's a db issue at a certain point
@@ -447,6 +447,7 @@ function ayGroupByTag(reportDataArray, tagContains) {
   \_____|______|_____|______|_| \_|  |_|   
                                            
 
+- 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
 - 1 todo: firefox schedule fix: https://github.com/vuetifyjs/vuetify/issues/14243#issuecomment-944907925