ayanova/devdocs/todo.txt

@@ -22,7 +22,7 @@ Prioritize anything that stands in the way of beta testing
 
 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?
 
 
 
@@ -189,12 +189,26 @@ TODO:
 	Virtualbox for testing setups:
 		this would be ideal for linux, windows server etc, there are even windows server prebuilt vms from microsoft for trial here:
 			https://developer.microsoft.com/en-us/windows/downloads/virtual-machines/
+			https://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-2019
+			PaSsWoRd123
+			https://serverfault.com/questions/908615/virtualbox-and-windows-10-cant-connect-to-a-server-hosted-on-virtualbox
 	IIS install 
 	this site has all the instructions laid out, just straight up follow, screenshot and copy into our manual as I do it here
 		https://www.findandsolve.com/articles/how-to-host-asp.net-core-application-in-windows-iis
 		https://docs.microsoft.com/en-us/aspnet/core/tutorials/publish-to-iis?view=aspnetcore-6.0&tabs=visual-studio
 		
 		https://docs.microsoft.com/en-us/aspnet/core/host-and-deploy/iis/?view=aspnetcore-6.0
+
+	IIS INSTALL NOTES DURING TEST INSTALL
+		Need password when install postgres so must update config.json to match
+		IIS install is exactly the same source files as the lan install, no need to have a separate installer, just network and standalone
+		Steps would be to ensure ayanova server can start first *then* configure through IIS
+			Unless inno can properly setup IIS with the correct settings
+			however I'm leaning towards manual setup as we had so much ongoing problems in v7 with wbi interfaces etc due to pre-existing shit 
+			and in fact it's only a few steps to get it working and half of them would apply even with an installer doing the work because the installer
+			can't get IIS installed if it wasn't already and if it was already isntalled it could just have a bunch of crazy shit pre-configured already 
+			that would conflict with an installer attempting to set up the site
+
 	Expert install see above
 		formalize this in a build and target folder, zip file should be versioned in name as well
 	LINUX Docker install see above