devdocs/deploy.md

@@ -103,16 +103,23 @@ NOTES:
 
 Once tests pass within expected parameters move on to next step
 
-## MOVE PRIOR VERSION INSTALLERS TO PREVIOUS
+## MOVE PRIOR VERSION INSTALLER TO "VAULT"
+
+### PREVIOUS FOLDER
 
 Clean out the previous previous download from the previous folder
-NOTE: if this is the final major release then it should go in the "old" folder in a dated or versioned sub-folder in case it needs to be resurrected at some future date
-
 Copy the existing downloads to the previous folder preserving (-p) the timestamps
 Change directory to the previous folder
 From the previous folder: cp ../\* . -p
 (note: will not copy folders so ok to use)
 
+### OLD FOLDER
+NOTE: Every posted release MUST go into this folder release then it should go in the "old" folder in a versioned sub-folder
+This is really important because users are eligible to download the final old release of their support and updates level so we will probably need to give out the urls to download old versions to people that didn't keep up to date
+
+
+
+
 ### DELETE CURRENT DOWNLOADS (or ignore and overwrite maybe easier and safer anyway)
 
 (OR JUST OVERWRITE THEM IS EASIER)

devdocs/todo.txt

@@ -1,25 +1,22 @@
 # now
 
 
-todo: TEST AND POST RELEASE BUILD 8.0.1	
-	Post in /next download folder for testing before posting fully
-	Re-run the smoke tests and e2e tests before posting 8.0.1 officially
-	*** todo: test on every platform every installer and be certain they work as advertised, yes this is a pain but it's necessary
-		going to need to re-install the virtualbox app, shit, no way around it though
-	Once all platforms pass all tests then and only then move to regular download folder and post about it on forum post
 
-TESTING:
-	Test on devops first
-		smoke, e2e basics
-	Install virtualbox
-		get a windows test edition for server and for regular windows
-	Test in virtualbox on Regular windows
-		TESTED Windows 11 works good, excellent in fact
-	Test in virtualbox on IIS server windows
-		fucking windows server 2022 stuck at password complexity right out of the gate setting it, trying abcABC123!@#
-		kWorked perfectly!!
-	Test in Virtualbox on desktop linux
-		for now just update and re-run, no sense in getting deep into this oen it's unlikely to be common and if it is it will work probably since server works.
+TODO: NEW SINGLE INSTALLER, DOCS AND ETC 
+	this is NOT it, need to make a single installer and docs without pg contained within first before can proceed to 
+
+HOLDUP: it's a mistake to have the single installer bunderl postgres isn't it?
+	what if pg needs to be updated outside of AyaNova?
+	What if AyaNova needs to be udpated and they install a new AyaNova installer and then pg is overwritten and the db is fucked up?
+	All those PG files take up a lot of space for archival purposes!
+	It's fragile and weird and not how PG was meant to be used!
+	The network install is almost a complete single standalone install just needs a bit of a tweak anyway!
+	Fuck, my gut kept telling me this but I ignored it way too much.... arghh
+	I only really wanted it so windows users could quickly try it out, but if we have a good online test strategy anyway then ultimately that's the way, plus the manual shows everything pretty comprehensively.
+
+todo: TEST AND POST RELEASE BUILD 8.0.1	
+	This is it! Post in regular download folder, empty the other folders with beta and shit, should only be the current release and maybe a copy on the historical, like when post next also post in history??
+
 
 
 PRICING AND PLANS THIS IS OFFICIAL HERE REPLACES ANYTHING WRITTEN ANYWHERE ELSE 2022-08-04 17:25:37