admin/raven
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Browse Source
This commit is contained in:
John Cardinal
2022-03-31 15:23:38 +00:00
parent 337624ded4
commit 156ef81b51
10 changed files with 92 additions and 56 deletions
Download Patch File Download Diff File Expand all files Collapse all files

59
devdocs/todo.txt
View File

@@ -1,7 +1,7 @@
# now
Import / export features
TODO:
OUTSTANDING FOR IMPORT:
@@ -9,52 +9,17 @@ TODO:
DOCS regarding missing boolean value in csv and info on not leaving empty
POST IMPORT TASKS
Test installer / upgrade
Linux server
- Ok, but needs upgrade shell script published somewhere
Linux Desktop standalone
TODO TEST DOCUMENT
Windows single standalone (should settle on naming scheme)
- OK, just stop the launcher if running, run setup, say no to overwrite config.json if edited, start the launcher
Windows lan
windows iis
once working and confirmed post update and upate the beta forum with NEW RELEASE
does forum working need to be changed to not only issues but new updates there as well?
"Known issues / updates"
Windows single would benefit from a backup and restore in a click kind of interface then could do the standalone install upgrade more easily?
Upgrade all our test servers wherever they may be
TEST FILE OPEN ON iPad device as the file input accept type may not work with apple
WINDOWS SINGLE LAUNCHER ISSUES:
Can windows single put it's db outside of the program files folder, i.e. can postgres be told to use a data folder instead?
only if it helps with the upgrade though, otherwise not much point
Opens the windows server web page as well as the AyaNova web app but that's confusing as the first page is the windows server
instead should just show the web app
Shutdown server in windows single gives error in server launcher window:
Shutting down Postgres database server...
Unhandled exception. System.InvalidOperationException: StandardIn has not been redirected.
at System.Diagnostics.Process.get_StandardInput()
at Program.<Main>$(String[] args) in C:\data\code\raven-launcher\Program.cs:line 98
Launcher might be better if it was an actual application with a button to open AyaNova UI in browser and a shutdown button and a log windows showing what is in the server UI
rather than a dos command line looking thing
Also that could be the UI to do a db back up and restore maybe for upgrade??
Linux desktop installer issues
There are two installers just becuase of config.json data path, consolidate?
rename to linux-x64 drop -server and -desktop?
why do I need *any* root rights, shouldn't it all just work or is it becuase of postgre?
why do I need to chmod desktop for ./AyaNova when it works on server without doing that?
Upgrade seems to be remove everything EXCEPT config.json from /usr/sbin/ayanova since there is no data there anyway
then unzip the new version and restart
Is /usr/sbin really the correct folder for the binaries?
INSTALL DOCS ISSUE
Says stopping and starting in one section but only talks about stopping
can there be a desktop icon to start the server like windows single?
get back to docs completion
@@ -204,6 +169,24 @@ todo:2 subscribe to all sources of security vulnerabilities that could apply to
.net core
front end vue & libs
todo: 3 WINDOWS SINGLE LAUNCHER:
Can windows single put it's db outside of the program files folder, i.e. can postgres be told to use a data folder instead?
only if it helps with the upgrade though, otherwise not much point
Opens the windows server web page as well as the AyaNova web app but that's confusing as the first page is the windows server
instead should just show the web app
Shutdown server in windows single gives error in server launcher window:
Shutting down Postgres database server...
Unhandled exception. System.InvalidOperationException: StandardIn has not been redirected.
at System.Diagnostics.Process.get_StandardInput()
at Program.<Main>$(String[] args) in C:\data\code\raven-launcher\Program.cs:line 98
Launcher might be better if it was an actual application with a button to open AyaNova UI in browser and a shutdown button and a log windows showing what is in the server UI
rather than a dos command line looking thing
Also that could be the UI to do a db back up and restore maybe for upgrade??
Windows single would benefit from a backup and restore in a click kind of interface then could do the standalone install upgrade more easily?
## DOCS
██████╗ ██████╗ ██████╗██╗ ██╗███╗ ███╗███████╗███╗ ██╗████████╗ █████╗ ████████╗██╗ ██████╗ ███╗ ██╗

4
docs/8.0/ayanova/docs/adm-import-customer.md
View File

@@ -21,7 +21,7 @@ Any field in the import file that is not listed on this page will be removed bef
- Tags
- WebAddress
- AlertNotes
- BillHeadOffice
- BillHeadOffice (MUST specify a HeadOfficeViz if this is true. This field must contain a value if supplied.)
- TechNotes
- AccountNumber
- ContractExpires
@@ -47,7 +47,7 @@ Any field in the import file that is not listed on this page will be removed bef
The following linked objects are supported for importing / updating:
- HeadOffice via "HeadOfficeViz" field which must contain the name of an existing HeadOffice
- HeadOffice via "HeadOfficeViz" field which must contain the name of an existing HeadOffice. BillHeadOffice must be included and set to true to use this field.
- Contract via "ContractViz" field which must contain the name of an existing Contract. If the Contract is specified then the ContractExpires field can be used to set the expiry date of the Contract. If ContractExpires is omitted then it is set to the import date and time minus 1 minute so that it won't take effect until it's been set to a future date.
## JSON file format

2
docs/8.0/ayanova/docs/adm-import-part-assembly.md
View File

@@ -136,5 +136,5 @@ The Items column **must** be:
Name,Active,Notes,Wiki,Tags,Items
Primary 7242,true,Corrupti et animi non soluta.,,"orange,silver,zone3,zone5","097091|1.00000,874579|3.00000,375486|1.00000,983612|15.00000"
Lower Arm 5369,true,Voluptatum et molestiae magnam at iste similique iusto modi ea.,,"orange,zebra,zone1","734629|1.00000,048902|1.00000"
Board 9995,true,Iure eius ut id consequatur omnis aut ut.,,"gold,mauve,violet,zone8","335219|1.00000|048902|1.00000,417318|1.00000"
Board 9995,true,Iure eius ut id consequatur omnis aut ut.,,"gold,mauve,violet,zone8","335219|1.00000,048902|1.00000,417318|1.00000"
```

10
docs/8.0/ayanova/docs/adm-import.md
View File

@@ -200,6 +200,16 @@ Each object type listed below links to a page showing the specific format requir
- ##### [Unit models](adm-import-unit-model.md)
- ##### [Vendors](adm-import-vendor.md)
## Import order when starting with a new AyaNova database
If you are getting started with AyaNova and importing your own data from other sources, several of the objects require other objects to already be present in the AyaNova database first.
- import Vendors before importing Parts, Unit Models or Units
- import Unit Models before importing Units
- import Part Warehouses before importing Part Inventory Transactions
- import Parts before importing Part Inventory Transactions or Part Assemblies
- import Head Offices before importing Customers
## Import form
#### Type

BIN
docs/8.0/ayanova/docs/img/ops-install-windows-lan-uncheck.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 19 KiB

After

Width:  |  Height:  |  Size: 22 KiB

4
docs/8.0/ayanova/docs/ops-install-windows-iis.md
View File

@@ -125,11 +125,11 @@ dotnet --list-runtimes
Once you have ensured the three requirements above are installed and available, download and run the AyaNova network installer: [https://www.ayanova.com/download/ayanova-windows-x64-lan-setup.exe](https://www.ayanova.com/download/ayanova-windows-x64-lan-setup.exe).
**IMPORTANT**: You MUST UNCHECK the option 'Start AyaNova server when Windows starts'
**IMPORTANT**: You **MUST UNCHECK** the option 'Start AyaNova server when Windows starts'
![SCREENSHOT OF setup window un checked server start with windows](img/ops-install-windows-lan-uncheck.png)
This is because IIS will be responsible for starting and stopping AyaNova. If you do select start with windows re-run the installer and uncheck it and finish the installation again.
This is because IIS will be responsible for starting and stopping AyaNova. If you accidentally select start with windows re-run the installer and uncheck it and finish the installation again.
Click next to continue to the next step:

2
docs/8.0/ayanova/docs/ops-upgrade-linux-server.md
View File

@@ -12,6 +12,8 @@ If you do not have a fresh backup there will be no way to recover from potential
### 2\. Upgrade
Ensure all other Users are logged out of AyaNova before proceeding.
The following shell script will automatically stop the AyaNova server service, remove the old AyaNova files, download and unzip the latest AyaNova files then start the server service.
Run the following shell commands:

8
docs/8.0/ayanova/docs/ops-upgrade-windows-iis.md
View File

@@ -1,7 +1,5 @@
# AyaNova Windows IIS hosted platform upgrade
The upgrade process involves stopping the AyaNova IIS site, replacing the AyaNova program files with the latest version and restarting the AyaNova IIS site.
These instructions assume the original installation steps were followed without changes, if you had to make changes adjust accordingly.
### 1\. Backup
@@ -16,6 +14,8 @@ If you do not have a fresh backup there will be no way to recover from potential
### 3\. Stop the AyaNova IIS site
Ensure all other Users are logged out of AyaNova before stopping the server.
Stop the AyaNova site in the IIS manager:
![image stop IIS site](img/ops-upgrade-windows-iis-stop-site.png)
@@ -24,7 +24,7 @@ Stop the AyaNova site in the IIS manager:
Run the setup file downloaded in step 2 above.
**IMPORTANT**: You MUST NOT CHECK the option 'Start AyaNova server when Windows starts'
**IMPORTANT**: Make sure the option 'Start AyaNova server when Windows starts' is NOT checked
![SCREENSHOT OF setup window un checked server start with windows](img/ops-install-windows-lan-uncheck.png)
@@ -58,4 +58,4 @@ Start the AyaNova site in the IIS manager:
![image start IIS site](img/ops-upgrade-windows-iis-start-site.png)
Open the AyaNova web app as you normally would, the login form will open in your browser and after a short delay you should see the page refresh and the new version number be displayed at the bottom of the login form.
Open the AyaNova web app in your browser, the login form will open in your browser and after a short delay you should see the page refresh and the new version number be displayed at the bottom of the login form.

56
docs/8.0/ayanova/docs/ops-upgrade-windows-lan.md
View File

@@ -1,13 +1,55 @@
# AyaNova Windows platform upgrade
# AyaNova Windows local network platform upgrade
Follow the upgrade instructions for your installation type below.
These instructions assume the original installation steps were followed without changes, if you had to make changes adjust accordingly.
## Single user upgrade
### 1\. Backup
### Local area network upgrade
Before proceeding, [make a backup](ops-form-backup.md) of the database **and** the attachment files and store it in a safe place.
AyaNova server running alone and access directly by users within a local office network.
If you do not have a fresh backup there will be no way to recover from potential data loss or damage.
### AyaNova server hosted through IIS upgrade
### 2\. Download setup file
AyaNova hosted via Microsoft Internet Information Server that is included with most editions of Windows.
[https://www.ayanova.com/download/ayanova-windows-x64-lan-setup.exe](https://www.ayanova.com/download/ayanova-windows-x64-lan-setup.exe)
### 3\. Stop the AyaNova server
Ensure all other Users are logged out of AyaNova before stopping the server.
To shut down the AyaNova server cleanly use the AyaNova web app form accessed from Server Operations -> Server State and the menu item [Shut down server](ops-server-state.md#shutting-down-the-ayanova-server).
Alternatively you can force close AyaNova using the ctrl-c key combination in the AyaNova launcher window.
### 4\. Setup
Run the setup file downloaded in step 2 above.
Keep the checkmark on _Start AyaNova server when Windows starts_ and click on _next_.
![SCREENSHOT OF setup window checkmarked server start with windows](img/ops-install-windows-lan-startup.png)
You will be prompted to go to the asp.net core download page:
![SCREENSHOT OF question about setup asp.net](img/ops-install-windows-lan-aspnetcore.png)
Select No.
You will next be prompted to go the PostgreSQL installer page:
![SCREENSHOT OF question about setup pgsql](img/ops-install-windows-lan-postgressql.png)
Select No.
The files will be updated and a final prompt will appear and ask if you want to overwrite the config.json file during setup:
![image prompt overwrite config.json file](img/ops-upgrade-windows-single-overwrite-config-prompt.png)
Select **Keep the existing file**.
If you select the overwrite option by accident you will need to re-edit the config.json file as you did during the [initial installation](ops-install-windows-lan.md#4-ayanova-server-configuration) once installation has completed before restarting the AyaNova server.
### 5\. Start the AyaNova server
![SCREENSHOT OF server desktop shortcut](img/ops-install-windows-lan-desktopayanovaserver.png)
Open the AyaNova web app in your browser, after a short delay you should see the page refresh and the new version number be displayed at the bottom of the login form.

3
docs/8.0/ayanova/docs/ops-upgrade-windows-single.md
View File

@@ -1,6 +1,5 @@
# AyaNova Windows single user platform upgrade
The upgrade process involves replacing the AyaNova program files with the latest version and restarting the AyaNova server.
These instructions assume the original installation steps were followed without changes, if you had to make changes adjust accordingly.
@@ -32,4 +31,4 @@ Run the setup file downloaded in the last step and follow the instructions.
Allow setup to _Launch AyaNova_ at the end of setup when prompted.
The login form will open in your browser and after a short delay you should see the page refresh and the new version number be displayed at the bottom of the login form.
The login form will open in your browser and after a short delay you should see the page refresh and the new version number be displayed at the bottom of the form.