removed references to digitalocean from docs in prep for SAAS (no need telling them how to do it without us)

devdocs/todo.txt

@@ -1,18 +1,39 @@
 # now
 
 
+todo: TEST digitalocean, set up a server in every data center far away from here, test ayanvoa on each one and see how peformant it is perceptually, i.e. does it even matter which server we're locating people on??
+todo: cheapest storage for attachments possible, test out creating a new droplet with block storage to hold the attachment files to see if it's possible, how it's done and mapped etc
+
+todo: metrics are fucked up for some reason
+	in fact I'd just like to reliably know how much disk space is in use etc, like the size of the db versus attachments in simple text
+
+todo: on ops server info page show main disk usage of db, attachments free memory in plain text unlike the metrics which are fucking useless
+
+todo: v8migrate Contracts in v7 were allowed to have no name, add code to invent a name on migration so it doesn't bomb
+
 todo: QBI don't check build date against expiry date if it's a trial, i.e. they can upgrade a trial all they want as long as it's not expired key
 
 todo: License agreement changes for SAAS customers, this is huge and I hadn't thought of it before, wording is very different in this case, fuck, need to wing it I guess
 	https://flgpartners.com/saas-pivots-transitions-perpetual-to-subscription-saas-models/
 	needs to be available separately in docs
 	Needs a disclaimer about the right to refuse service if becomes too high usage i.e. subject to usage limitations to cover our ass and check with D.O. how to clamp that from going into expensive territory for us?
+	We also need to mention we will size their servers to adequate work load or whatever meaning we will put them on the smallest cost server that will sustain their needs.
 
 
 todo: ROCKFISH different license key signature if it's a SAAS license
 	this solves a lot of problems, effectively it's unlicensed if they move their data to their own hardware without a key
 	requires that AyaNova have different internal key to check, maybe it's actually a build switch for that since only we will be running our SAAS version.
 
+todo: ROCKFISH can't make a trial key for users in the UI, only when it's requested from ayanova.
+	I'm really not sure if this is an issue or not but putting it on the list in case
+
+todo: DOCS - remove all mention of digitalocean from the install and other docs since we're going to be using them for SAAS we don't want to make it simple for people to host themselves, just say Linux and leave it at that.
+
+
+todo: RENTAL terminology needs to change to "SUBSCRIPTION" in rockfish and in client and at server, RENT should not appear anywhere, it's awkward and old fashioned
+todo: SUBSCRIPTION should only refer to month to month SAAS feature / plan.  Support and upgrades should be referred to as Maintenance or Support and upgrades without the word "subscription"
+TODO: above changes at SHAREIT with the product descriptions as well so no confusion
+
 todo: if SAAS needs to do some things differently:
 	if it helps, consider a different build flag since SAAS is like an internal build for us
 	SERVER - count total active users towards license not techs only
@@ -34,7 +55,8 @@ todo: if SAAS needs to do some things differently:
 		maybe it's a plust because we can say you get a maximum storage for attachments of XXGb based on droplet size and it's an add-on to go with a bigger server??
 		Because some people need it and will pay for it if it's offered.
 	SERVER - how to cap bandwidth, storage, whatever we get billed extra for from d.o.
-	
+	CLIENT - NEEDs to report that a new version was installed to the user with link to changes when we publish a new version so they can be made aware
+	EMAIL - research how to send emails with a reliable provider i.e. sendgrid or alike and what the costs and add-on price for that would be.
 
 todo: each droplet for SAAS would need it's own ssh key and password to avoid eggs in one basket security scenario
 	also would need to securely store the passwords somewhere really really fucking secure like offline in a special keypass only accessible from certain hardware maybe with a digital key or something I dont' know
@@ -68,7 +90,7 @@ todo: SAAS different license checking method to ensure only *we* are hosting it
 
 
 
-todo: test out creating a new droplet with block storage to hold the attachment files to see if it's possible, how it's done and mapped etc
+
 todo: test out automatic backups using digitalocean's built in system with their pricing and how that would work with our backup system for the db etc
 
 
@@ -180,6 +202,7 @@ todo: validate the rate limiting by tailing the error log and hitting test raven
 
 todo: QBOI deprecation
 	BUT...this is probably going to be needed for future again so keep on back burner 
+	YES: EVERYONE OF OUR COMPETITORS THAT HAS ANY QB HAS QBONLINE it's the desktop that is rarer
 	done: QBOI removed from website except still in docs and in trial installer
 	done: Product is set to inactive with ShareIt, no one can buy it now
 	OUTSTANDING: I will need to remove it from the AyaNova installer completely