ayanova/devdocs/todo.txt

@@ -171,33 +171,47 @@ Coded by importance
 ██║██║╚██╗██║╚════██║   ██║   ██╔══██║██║     ██║     
 ██║██║ ╚████║███████║   ██║   ██║  ██║███████╗███████╗
 ╚═╝╚═╝  ╚═══╝╚══════╝   ╚═╝   ╚═╝  ╚═╝╚══════╝╚══════╝
-                                                      
+
+User types and complexity:
+	Just want to get going immediately and no technical stuff:
+		hosted solution by us
+	Want to run locally on windows / beta test migration, our typical existing user (except external access users)
+		self install to windows with everything ready to run out of the box (this installer I'm making now)
+	Shared power users with external access 
+		Zip file install for power users, archive with manual guidance
+		need to figure out how to support certs in ayanova etc as nginx is shit on windows
+	Linux direct to the docker solution initially, later can see about a tar archive and bare metal running it
+
+
 ## WINDOWS
-- launcher to make sure it starts and works properly with Windows 	
+
-	Windows forms app??
+### Simple with postgres for one click install and run
-		minimize to tray so doesn't need to be a "service"
+This version is for users who do not have a pg server and don't want to configure anything but just start working
-	can start from windows startup program files system so doesn't need to be a service
+has launcher to start pg, ay, then browser and closes all when they exit the launcher ctrl-c
-	writes or logs to screen any startup issues
+preconfigured with sane defaults, data goes to programdata/ayanova folder (v7 did ayanovadata so this differentiates)
-	plays the role of the batch file currently in use
+Needs appsettings.json file included that it reads on boot and is beside the ayanova.exe file
-	Also can configure through the launcher, maybe it writes out a config file if the config code can also read that
+this is a sample to modify with the critical settings (or all settings with their defaults set so user can edit at will later)
-	or command line (though it has to store it somewhere so one way or another maybe a new config.txt file??)
+
-	Launcher should have sane defaults so user can just start it and start using it but configure as they please later
+Just replicate the batch file but properly and in order and in fixed location so can regen the data easily backup easily etc 
+
+No built in config ability, edit json file only if necessary but make it not necessary, this is meant to be a single standalone quickie for neophyte users
+
+
+{
+    "AYANOVA_USE_URLS": "http://*:7575",
+    "TransientFaultHandlingOptions": {
+        "Enabled": true,
+        "AutoRetryDelay": "00:00:07"
+    },
+    "Logging": {
+        "LogLevel": {
+            "Default": "Information",
+            "Microsoft": "Warning",
+            "Microsoft.Hosting.Lifetime": "Information"
+        }
+    }
+}
 	
-	Launcher responsibilities
-		Works with standalone as a quick way to start AyaNova for single user but also..
-		Works with shared network install
-		May even need to do NGINX stuff??
-			or maybe generated a config for nginx?
-			Fuck, it would be nice if ayanova could directly service and work with letsencrypt etc to avoid nginx entirely
-			
-		configuration page with defaults for *all* config settings
-		help with settings where necessary
-		confirms ports availability
-		confirm sql
-		start sql if standalone 
-		launch server
-		start browser window once server confirmed to start
-		START / STOP server
 
 With launcher, inno only needs to drop files and put desktop icon