todo.txt

@@ -1,6 +1,26 @@
 
-client - open / edit all the things
+LICENSE NOTES
 
+Sockeye should generate a license on a sale receipt, maybe after a slight delay. Generated license should be in the list of licenses but have a unfulfilled status of some kind so it's ready for me to visually see purchases applicable and confirm approve and send it with one click but it's not doing it itself.
+
+If more purchases come on that supply to take customer for v7 then it should regenerate a new license or I guess edit the one it made before and just add to it.
+Idea bring that all I have to do is open they list off licenses and just release any that are good to go.
+UI should show the purchases that go into a license so can confirm visually without having to click anywhere else.
+
+This way is all but automatic in pero for full automation later.
+Maybe even a semi automatic dead man switch that will just send it after 24 guess if I don't once it's confirmed to work properly.
+
+So need properties added to license object for fulfilled status and a property indicating sent to customer and a menu options to send manually maybe too.
+
+I guess will need a template for email messages as well.
+Tier into notification system.
+Don't forget some licenses are not done through SHAREitb do must support manual generation from Paypal etc
+
+ALSO 
+
+Needs manual license generation for v7 still
+
+=========
 
 PURCHASE drives new licensing ui
 To automate as much as possible need following:
@@ -71,4 +91,42 @@ Also, sidebar, check if can pay d.o. in advance, or do I want that??
 new roles and bizroles set appropo
     Developer - rw cases
     Support - read cases, read sales and customer data?
-    Sales - licenses
+    Sales - licenses
+
+
+
+    ==============================
+    certbot expand
+
+    root@devops:/etc/nginx/sites-available# certbot --nginx --cert-name test.onayanova.com -d test.onayanova.com,subtest.onayanova.com
+Saving debug log to /var/log/letsencrypt/letsencrypt.log
+
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
+You are updating certificate test.onayanova.com to include new domain(s):
++ subtest.onayanova.com
+
+You are also removing previously included domain(s):
+(None)
+
+Did you intend to make this change?
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
+(U)pdate certificate/(C)ancel: u
+Renewing an existing certificate for test.onayanova.com and subtest.onayanova.com
+
+Successfully received certificate.
+Certificate is saved at: /etc/letsencrypt/live/test.onayanova.com/fullchain.pem
+Key is saved at:         /etc/letsencrypt/live/test.onayanova.com/privkey.pem
+This certificate expires on 2023-04-04.
+These files will be updated when the certificate renews.
+Certbot has set up a scheduled task to automatically renew this certificate in the background.
+
+Deploying certificate
+Successfully deployed certificate for test.onayanova.com to /etc/nginx/sites-enabled/default
+Could not install certificate
+
+NEXT STEPS:
+- The certificate was saved, but could not be installed (installer: nginx). After fixing the error shown below, try installing it again by running:
+  certbot install --cert-name test.onayanova.com
+
+Could not automatically find a matching server block for subtest.onayanova.com. Set the `server_name` directive to use the Nginx installer.
+Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.