devdocs/pricing.md

@@ -50,7 +50,8 @@ NEW PERPETUAL V8 PRICING AND SYSTEM
 Subscription only, no different up front cost, you pay per year for a years worth of support and updates and can stop before the next year renewal and be fixed at that release version.
 $2/user per month or 24 per user per year, minimum 3 users
 
-$24/year per **active login user** minimum 3 users for perpetual unlike subscription which has no minimum
+$24/year per **active login user** minimum 3 users for perpetual unlike subscription which has no minimum 
+(Note that the minimum 3 is because a single at 24 bucks wouldn't be worth our time to deal with support and updates and administration and perpet are deliberately priced far cheaper per user so it's not a big jump for single people)
 1-3 **users** = $72.00 charge to customer / $66.17 net profit
 5 users = $120 charge / $112.25 net profit
 10 users = $240 charge / $227.45 net profit

devdocs/todo.txt

@@ -6,8 +6,6 @@ TODO: Get minimum server size vs user count so can sell it properly
 
 
 
-
-
 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?
@@ -30,7 +28,61 @@ todo: test devops as production server with automated backups, upload a range of
 
 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
+
+todo: v8migrate MUST have a copy button to copy the output so people can easily send it, currently it has none which is a huge fucking oversight
+
+todo: v8 migrate MUST have a warning to *NOT* login as superuser during migration as one of the popup dialogs just before it starts migration
+
+todo: Migration instructions in manual Must mention that superuser won't see the migrated data and must make a user to do so:
+
+Good morning Dave, we don't have access to your data here but it's likely you are logging in as the "superuser" account which only has access to AyaNova setup and configuration related operations, it can't be used to view business data.
+
+I'll make a note to mention that in the migration instructions, it doesn't appear to be there.
+
+The migration process migrates all users without rights to login so what you will need to do next to do is login as superuser, go to Administration -> Users and either create or modify an existing User that was migrated, set them to Active and AllowLogin give them access to all the Roles and save that record and then you can login as that user and view all the data that was migrated.
+
+Note that there is a copy of the migration log sent to the SuperUser account as a memo which contains the migration information but also instructions on what to do next *after* migration and one of those steps is to enable users to login and set their authorization roles and passwords etc.
+
+These things are not migrated automatically for security reasons and because they don't translate from v7 to v8 in the case of individual rights and roles which are simplified greatly in AyaNova 8.
+
+- John
+
+
+
+On 2022-09-19 8:41 AM, dave morrowservice.com wrote:
+>
+> Hi John,
+>
+> Can you tell if I imported everything? Because We can’t find anything that looks like Clients, Workorders, Instruments/Units or anything really that is recognizable. Did we miss something?
+>
+>  
+>
+> Thanks, Dave
+>
+>  
+---------------------
 .........................
+
+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 
+
 reorganize below and then whatever is most urgent