From 4147b3bd44da8197cfc61ad8a99d363268e71498 Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Mon, 21 Feb 2022 19:16:26 +0000 Subject: [PATCH] --- .../ayanova/docs/ops-install-linux-desktop.md | 4 +++ .../ayanova/docs/ops-install-linux-server.md | 25 ++++++++++++++++--- .../ayanova/docs/ops-install-windows-iis.md | 6 ++++- .../docs/ops-install-windows-single.md | 4 +++ 4 files changed, 35 insertions(+), 4 deletions(-) diff --git a/docs/8.0/ayanova/docs/ops-install-linux-desktop.md b/docs/8.0/ayanova/docs/ops-install-linux-desktop.md index 165abf4c..a26bb7d4 100644 --- a/docs/8.0/ayanova/docs/ops-install-linux-desktop.md +++ b/docs/8.0/ayanova/docs/ops-install-linux-desktop.md @@ -164,6 +164,10 @@ Open your web browser and navigate to the AyaNova server URL. Assuming the defau 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. Alternatively you can hard shut down AyaNova using the ctrl-c key combination in the terminal console window where AyaNova is running however this is not recommended. +## Report rendering first time delay + +The very first time a report is rendered in AyaNova there will be a delay while the chromium browser report rendering components are installed. + ## Getting started and using AyaNova The next step is to [login](ay-start-login.md), request or install a [license](adm-license.md) and if are trying out AyaNova for the first time follow the [evaluation trial guide](ay-evaluate.md). diff --git a/docs/8.0/ayanova/docs/ops-install-linux-server.md b/docs/8.0/ayanova/docs/ops-install-linux-server.md index 6888a267..06249910 100644 --- a/docs/8.0/ayanova/docs/ops-install-linux-server.md +++ b/docs/8.0/ayanova/docs/ops-install-linux-server.md @@ -363,6 +363,10 @@ sudo ufw allow 'Nginx Full' NGINX needs to be configured to reverse proxy to AyaNova server. +If you are already using NGINX then examine the following and adapt it to your existing configuration, if you have no existing NGINX services skip to the next section to create one for AyaNova. + +##### Existing NGINX services + If you are already using NGINX for other services then a site configuration file entry will need to be made to reverse proxy AyaNova with appropriate settings for your site. We cannot provide details for that as it must work with your existing NGINX configuration, however here is an example of the AyaNova specific parts only taken from a working site that uses Let's Encrypt certificates to give an idea of what is required: ``` @@ -388,6 +392,8 @@ server { } ``` +##### Completely new NGINX service for AyaNova only + If this is a **new install dedicated to AyaNova only** and no existing NGINX services or websites will be impacted then replace the `default` NGINX configuration file as follows: Switch to the NGINX configuration folder: @@ -404,6 +410,14 @@ cp /etc/nginx/sites-enabled/default ~/nginx-default-backup Open the existing `default` config file in an editor, replace it's contents **entirely** with the following configuration and save: +If using Nano text editor: + +```bash +sudo nano default +``` + +delete all text and replace it with this text: + ``` server { listen 80; @@ -446,9 +460,10 @@ sudo systemctl restart nginx #### Confirm DNS has propagated -Confirm that you can now navigate to AyaNova web app login page through regular un-encrypted HTTP via the domain name configured earlier. i.e. `http://ayanova.yourdomain.com` or `http://yourdomain.com` if not using a subdomain. +Confirm that you can now navigate to AyaNova web app login page through **un-encrypted HTTP** via the domain name configured earlier. i.e. `http://ayanova.yourdomain.com` or `http://yourdomain.com` if not using a subdomain. + +Once DNS has propagated and you see the AyaNova web app login page (or license agreement page) over **unecrypted** HTTP it's time for the next step. -Once DNS has propagated and you see the AyaNova web app login page over unecrypted HTTP it's time for the next step. If DNS has propogated but you see an NGINX error page instead, confirm that AyaNova server is up and running and re-check the NGINX configuration. ### Add domain name to NGNIX config @@ -517,7 +532,11 @@ Certbot will also install a systemd timer event which will auto-renew the SSL ce Confirm that you can now navigate to AyaNova web app login page through encrypted HTTPS via the domain name configured earlier. i.e. `https://ayanova.yourdomain.com` or `https://yourdomain.com` if not using a subdomain. -You should now see the login page through an encrypted SSL connection and AyaNova is ready for use. +You should now see the login (or license agreement) page through an encrypted SSL connection and AyaNova is ready for use. + +### Report rendering first time delay + +The very first time a report is rendered in AyaNova there will be a delay while the chromium browser report rendering components are installed. ## Getting started and using AyaNova diff --git a/docs/8.0/ayanova/docs/ops-install-windows-iis.md b/docs/8.0/ayanova/docs/ops-install-windows-iis.md index 9817ed64..13dfb53d 100644 --- a/docs/8.0/ayanova/docs/ops-install-windows-iis.md +++ b/docs/8.0/ayanova/docs/ops-install-windows-iis.md @@ -260,7 +260,7 @@ Save the recycle time once entered and click on Ok to save and continue to the n #### Open AyaNova app through IIS -Right click on the AyaNova site created earlier in IIS Manager and select "Manage website" and then "Browse". The AyaNova web app should open to the login page. +Right click on the AyaNova site created earlier in IIS Manager and select "Manage website" and then "Browse". The AyaNova web app should open to the login (or license agreement) page. If you receive an error message from IIS "HTTP Error 500.19 - Internal Server Error The requested page cannot be accessed because the related configuration data for the page is invalid." This generally means you did not follow the steps in the correct order and ASP.NET Core was installed **before** IIS was enabled which means IIS doesn't have the proper handlers to run an ASP.NET Core application. In order to fix this run the ASP.NET Core hosting bundle setup again that was installed previously (repair installation) to ensure IIS is setup with the correct handlers. @@ -278,6 +278,10 @@ For connection from the internet your network adminstrator will need to setup II Let's Encrypt provides free SSL certificates and lists [several Windows clients](https://letsencrypt.org/docs/client-options/#clients-windows-/-iis) for use with Let's Encrypt on Windows. +### Report rendering first time delay + +The very first time a report is rendered in AyaNova there will be a delay while the chromium browser report rendering components are installed. + ## Getting started and using AyaNova The next step is to [login](ay-start-login.md), request or install a [license](adm-license.md) and if are trying out AyaNova for the first time follow the [evaluation trial guide](ay-evaluate.md). diff --git a/docs/8.0/ayanova/docs/ops-install-windows-single.md b/docs/8.0/ayanova/docs/ops-install-windows-single.md index 52cccb49..6d0f16c0 100644 --- a/docs/8.0/ayanova/docs/ops-install-windows-single.md +++ b/docs/8.0/ayanova/docs/ops-install-windows-single.md @@ -42,6 +42,10 @@ The single user installer will use TCP/IP ports 6432 for the PostgreSQL server a To shut down the AyaNova server press the ctrl-c key combination in the ayanova-launcher window. To start the AyaNova server use the installed desktop or start menu icon to run the ayanova-launcher. +## Report rendering first time delay + +The very first time a report is rendered in AyaNova there will be a delay while the chromium browser report rendering components are installed. + ## Getting started and using AyaNova The next step is to [login](ay-start-login.md), request or install a [license](adm-license.md) and if are trying out AyaNova for the first time follow the [evaluation trial guide](ay-evaluate.md).