ayanova/devdocs/todo.txt

@@ -1,7 +1,7 @@
 @@@@@@@@@@@ ROADMAP STAGE 2:
 
 PRIORITY - ALWAYS Lowest level stuff first, i.e. TODO at server, api route changes etc then back here in order lowest level first as affects the most stuff exponentially so best to do it early
-vabshardbodieshipbones
+
 =-=-=-=-
 
 
@@ -10,15 +10,10 @@ todo: Test run on v7 laptop
 	https://www.ayanova.com/Downloads/v8/ayanova8.alpha.8-win-x64.zip
 
 
-todo: Open object handler for backup errrors out
-	to test, force a backup then go to admin-history 
 todo: UI for restart serial number route for widget?
 	Not tested nor ui'd yet
 
 
-todo: Replicate above but for Linux in a shell script to run everything then test on linux (not devops obvs) as a standalone app
-	gonna need a linux vm maybe?  This comes up repeatedly, maybe I should just use DO server like forum or something or mail backup, low load one that can be crashed without bringing down important shit
-
 =========================================================================================================
 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
 @@@@@@@@@@@@@@@ ROADMAP STAGE 3
@@ -224,14 +219,13 @@ TODO: ON UPDATE TO NEW version
 
 
 
-todo: INSTALLER
+todo: WINDOWS INSTALLER
 	Runner harness wrapper thing?
 		even if windows only
 		it could modify config since it's outside the server
 		check for Postgres server extant and if not automatically start the standalone postgres instance
 		manage postgres start and stop and configuration changes, sit in tray, run AyaNova server from there?
-		Linux users don't mind doing the manual config thing as much, they're used to it and it could just be a shell file anyway
-
+		
 	easy way to select command line params without resorting to editing text files for end user
 		initially it's an installation option, but then need to edit after the fact
 	Quick check of installers available still and is it still kosher to keep using INNO setup or is something better, more supported by windows etc?
@@ -249,6 +243,18 @@ todo: INSTALLER
 	I want short targetted testing only, not someone downloading and trying it out a month later, that's useless for us
 	This needs to be focused on what I need to get from people about testing
 
+
+todo: LINUX INSTALLER
+	Linux users don't mind doing the manual config thing as much, they're used to it and it could just be a shell file anyway
+	So mainly this would be a documentation steps to install type issue
+	
+
+todo: DOCUMENT DOCKER 
+	Present dockerfile maybe for docker installation with FILES folder pre-ready to build / run
+	Whatever docker needs
+	Or maybe private registry with docker images on our servers somewhere
+
+
 todo: Suggestion box:	BETA MODE Feedback form?
 		There is a suggestion box case here somehwere
 		Sends errors, server log, suggestions etc, directly to rockfish?