TODO:
Modify QBOI to use the new token system but just statically coded in and do a test build and see if can access and do ops via qboi with sample data
Use the QBridge code as is to fetch a token for testing, build qboi with the token embedded and see if it works.

If that works then plan and institute a publishable solution.
    - We don't want to store their tokens if possible so try to do it without any token storage
    - Maybe they generate a one time code that they send to the Start route which in turn they can fetch from memory off the server later via qboi
    - QBOI only holds the token until they fetch it via qboi
    - QBOI probably will be able to refresh the token any time as there is no redirect url required for refreshment
    - So QBridge is only required for the initial authorization process after which QBOI can operate using the refresh token scheme until that expires at which point QBOI can simply redirect to the QBridge again
    


***********************
DEPLOYMENT qboauth.ayanova.com
***********************
1) CLEAN out /publish folder (used by all netcore utils)


2) PUBLISH
publish command line from C:\data\code\qbridge folder:

//this will build a release version which is what we use on the server now
//DEPRECATED dotnet publish -c Release -o ./../publish/
//this will build for our ubunutu linux server
dotnet publish -c Release -o ./../publish/ --no-self-contained -r linux-x64


//if need a debug version
dotnet publish -o ./../publish/

3) COPY

## MAKE BACKUP FIRST: cp -R pecklist pecklist_backup

Copy over to production server, only need the .dll and the wwwroot folder contents, 
remember not to delete the folders on the server only replace their contents because there are file permissions set
Backup the database

4) Delete any test data local here


Restart the service on the server:
systemctl status kestrel-qboauth.service
systemctl start kestrel-qboauth.service
systemctl stop kestrel-qboauth.service