devdocs/todo.txt

@@ -2,10 +2,16 @@
 
 
 
-TODO: Get minimum server size vs user count so can sell it properly
+todo: test devops as production server with automated backups, upload a range of attachments,  simulate crash and restore etc, run load test then backup etc see disk space consumption and make sure 
+	backup works adn restore works as this is obvsiouly critical.
+	IN PROGRESS: set devops to backup at 10pm tonight
+	Tommorrow morning download backup, erase all data, restore it, document the process for subscription server
+	Also check the docs I must have documetned it there but if not then document that shit
 
 
 
+CLIENT CHANGS TO DO NOW
+
 STRIP OUT METRICS (maybe some of them for both types, just not working or accurate, the db and file size stuff is useful if working properly)
 OPS - subscriptions don't need almost all of ops nor should they have it, is any info leaking that shouldn't go through it remove with a machete (tied to build type)
 DOCS - ops section of docs not relevant to subscribers, add "PERPETUAL BUILD ONLY" maybe at top or something?
@@ -13,37 +19,24 @@ METRIC WE DO NEED
 	just a simple value showing storage space available for subscribers maybe usage over time?
 	but surface outside of OPS tree in menu, in admin? backup?
 
-todo: should alert users if low on disk space in dedicated subscription volume
+todo: should alert users if low on disk space in dedicated subscription volume	
+	in central location maybe server information or license page or whatever
 
 todo: Seeding, maybe just offer one size of seeding for trialers, there's no real use to us to offer more levels for marketing or testing
 	people just want to try all features, v7 only had 20 workorders
 	Keep ability for us for load testing etc, but don't offer it in the UI
-	
+	YES DO THIS FOR PERPETUAL AS WELL AS SUBSCRIPTION, CHECK DOCS TO MAKE SURE IT"S NOT MENTIONED ANYMORE	
 
 todo: on a night run with full generation see how big the db actually gets, it's surprisingly time consuming to erase it right now during testing
 	note this is important to see over time how big it gets with a continual heavy load
 
-todo: test devops as production server with automated backups, upload a range of attachments,  simulate crash and restore etc, run load test then backup etc see disk space consumption and make sure 
-	backup works adn restore works as this is obvsiouly critical.
+todo: document subscription server maximum attachment is 25mb unless they ask us to change it, actually for a subscriptin we might want to decrease that
+maybe more like 5mb or something?? Need to look into it
+But overall that would be a good thing to be able to show in the User interface if possible...hmmm..how to do that is tricky
+can it read the nginx config file? Not likely.  Maybe the config file can return a value
+
 
-TODO: Make soem SSH keys pre uploaded to DO for customers in actual usage, can't use the same key for all customers so maybe document the process of
-how to make a key quickly and do that
 
-todo: backup service pricing and product code for sales in shareit
-	This is where we backup their data for them to spaces "off server" for a fee
-	this needs to be a  zip file that only takes the most recent backup file available
-	and we need an alerting system to check if it's working, so do it manually at first
-	otherwise they have chosent NOT to pay for backup service so they must download a copy of their backup
-	maybe it's a charge per gb?  Or flat cost since spaces is relatively cheap
-	Needs a unique zip backup code for each site following a system of some kind
-	maybe each customer gets a unique value that is not guessable by anyone and used for their db account etc
-	
-	
-todo: Need a place to store secrets, maybe in rockfish itself makes the most sense, but how secure is that?
-	it needs to be secure enough to store customer ssh passwords and db password and backup zip password
-	hashicorp vault thing?  Rockfish queries it for the password or is this just indirection but not really secure?
-	In the mean time I need a system for right now, keepass maybe sb for personal stuff only as it's online and have a 
-	separate keepass db that is only in one file not put online with the secrets in it here locally and backed up the wazoo
 
 todo: v8-migrate MUST open up server again and not leave locked , morrow had thought migration was done then couldn't login said it was erasing database
 
@@ -54,7 +47,7 @@ todo: v8 migrate MUST have a warning to *NOT* login as superuser during migratio
 TODO: Migration doesn't indicate there was an error properly, it's the same dsiplay at the end regardless, it should *NOT* show export completed like normal if there was an issue 
 
 todo: v8-migrate may encounter parts with no part number which will break migration if part number is the primary identifier going into name (and vice versa if the setting for part name is using v7 name and is empthy etc).  For purposes of successful migration it should check at the last moment before sending if the part name in v8 will be empty and substitute a temporary value 
-
+Actually, any bloody thing without a name should do this shouldn't it?  Why not?