devdocs/pricing.md

@@ -51,6 +51,7 @@ Subscription only, no different up front cost, you pay per year for a years wort
 $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 
+(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
 
 

docs/8.0/ayanova/docs/ops-import-v7.md

@@ -134,13 +134,69 @@ Note that Windows may prompt you that the installer is "unsigned" from an "unkno
 
 Continue with the next step:
 
+## How to break the migration
+
+If you login as the SuperUser account in AyaNova 8 while the migration is in process you will immediately crash the migration and see an error like this in the migration log:
+
+`E2004 - Authorization token replaced by more recent login`
+
+Followed by a stream of errors.
+
+Do not login to AyaNova 8 until migration has completed or stopped due to error to avoid this problem.
+
 ## Running the migration
 
 -   Avoid future problems: If you haven't already, read _all_ of this document before proceeding
 -   Multi-user only: If migrating from a networked multi-user AyaNova 7.6+ installation, now is the time to ensure all users are out and networked Generator service is stopped. **Do not proceed until this is verified or the data may be corrupted**
 -   Login to AyaNova 7.6+ as _the_ Administrator / manager account, it's required to be this exact account, not another one
 -   Select the "V8 Migrate" plugin in AyaNova 7 from the main window plugin menu and the login and server URL dialog will open
--   Enter the URL of your AyaNova 8 server. There is a "Test URL" button to optionally confirm if you have entered the correct address or not.
+-   Enter the URL of your AyaNova 8 server. The easiest way to get this is to simply copy the entire URL displayed in the browser from the AyaNova 8 web application web page, for example the login page.
+-   There is a "Test URL" button to confirm if you have entered the correct address or not.
 -   Enter your AyaNova 8 SuperUser account login credentials. No other account is permitted to perform this operation. The default SuperUser account login name is "superuser" and password is "l3tm3in" if it has not been changed.
--   A form will popup and show the progress of the Migration operation. There is no easy way to estimate how long this will take which is why several test migrations should be done before the final migration. Time of migration depends on the network latency and speed between the V8 Migrate plugin and the AyaNova 8 server as well as the number and complexity of objects entered into AyaNova and the quantity and size of files that may need to be uploaded.
--   When the migrate is finished you will be able to login to V8 and start [setting things up](ay-biz-admin-migrate-v7.md)
+-   A **Migration log** form will popup and show the progress of the Migration operation including any errors or specific action required for your particular data.
+- Do **NOT** login to the AyaNova 8 server while migration is taking place, it will crash the migration completely.
+-   There is no easy way to estimate how long migration will take which is why several test migrations should be done before the final migration. Time of migration depends on the network latency and speed between the V8 Migrate plugin and the AyaNova 8 server as well as the number and complexity of objects entered into AyaNova and the quantity and size of files that may need to be uploaded.
+
+## After the migration
+
+When migration has completed you should review the migration log entries displayed _before_ closing the migration plugin in order to check the status of the overall migration and look for errors.
+
+### Success
+
+If it was successful you will see a similar display to this:
+
+![success migrate log example](img/ops-import-v7-log-completed-success.png)
+
+### Failure
+
+If it failed you will see a line in the log similar to this:
+
+`2022-09-19T12:05:36 Export failed with error:`
+
+followed by the details of the problem.
+
+In some cases an error may indicate an issue that you can fix yourself such as an AyaNova 7 item missing a Name or may be something technical that should be sent to AyaNova support in which case please click into the log with your mouse and drag and highlight all the text, right click to copy and then paste the entire log into an email and send to Support for resolution.
+
+If the error is of a type that doesn't prevent it, the migration plugin will attempt to [send a memo](#post-migration-instructions-memo) to the SuperUser account with a copy of the migration log.
+
+### Where is my data?!
+
+The SuperUser account does not have the ability to view business data such as Customers and Work orders in the AyaNova 8 user interface so you will not see that type of data when logged in as the SuperUser account.
+
+Migrated v7 Users are automatically migrated as in-active and do not have any authorization Roles set as a security precaution.
+
+To view your migrated data you will need to create or edit a migrated User by logging in as the SuperUser and then create a new User or edit one of the migrated Users to have full a full access role such as `Business administration`, checkmark `Active`, `Allow login` and give them a login name and password, then login as that User to view the migrated data.
+
+### Post migration instructions Memo
+
+After a migration has completed a Memo is sent to the AyaNova 8 SuperUser account with specific steps to take after migration **personalized** to _your_ particular data depending upon what it finds during the migration process.
+
+These steps should not be ignored, they are important to get started using AyaNova as soon as possible with minimum hassle.
+
+To view the Memo login as the SuperUser account and navigate to the list of Memos:
+
+![migrate memo navigation](img/ops-import-v7-memo-nav-superuser.png)
+
+And open the migration memo:
+
+![migrate memo open](img/ops-import-v7-memo-open.png)

docs/8.0/ayanova/mkdocs.yml

@@ -7,7 +7,7 @@ theme:
 site_name: AyaNova manual
 site_dir: '../../../server/AyaNova/wwwroot/docs'
 strict: true 
-copyright: Copyright © 2022 Ground Zero Tech-Works Inc. REV-2022-09-12
+copyright: Copyright © 2022 Ground Zero Tech-Works Inc. REV-2022-09-19
 extra:  
   generator: false
 # Extensions