Add linux install instructions

Author: webprofusion-chrisc

docs/hub/guides/ccm.md

@@ -1,5 +1,5 @@
 ---
-title: Using with Certify Certificate Manager
+title: Joining the Hub
 ---
 
 ## Summary

docs/hub/installation/containers.md

@@ -1,6 +1,6 @@
 ---
 id: containers
-title: Docker and other container platforms
+title: Install for Docker and container platforms
 ---
 ### Docker 
 :::info

docs/hub/installation/index.md

@@ -12,7 +12,7 @@ You can install the *Certify Management Hub* using docker, various Linux distrib
 
 - [Docker and container environments](containers)
 - [Windows](windows)
-- Linux
+- [Linux](linux)
 - macOS
 
 The product runs in Community Edition mode by default, see [Licensing](../../guides/licensing.md) for more information.

docs/hub/installation/linux.md

@@ -0,0 +1,68 @@
+---
+id: linux
+title: Install for Linux
+---
+
+## Certify Management Hub
+
+If you just want to try out the Management Hub and easy way to do that is to use [docker or other container tool](containers.md). However if you want to install the Management Hub (or Management Agent) directly you can do that as well.
+
+#### Scripted Install
+The following commands:
+- Download the latest version, ensuring any old download and old install files are removed if present
+- Extract the downloaded archive to the temporary ./certify-hub-install path
+- Runs the install script to install under /opt/certify-hub, and sets up the hub as a systemd service called `certify-hub`, running as user `certify`.
+
+```
+rm ./certify-hub-linux-x64-latest.tar.gz -f
+wget https://certifytheweb.s3.amazonaws.com/downloads/archive/beta/hub/certify-mgmthub-linux-x64-latest.tar.gz
+rm -rf ./certify-hub-install && mkdir -p ./certify-hub-install
+tar -xvf certify-mgmthub-linux-x64-latest.tar.gz -C ./certify-hub-install
+sudo ./certify-hub-install/scripts/install-hub.sh
+```
+
+Note: for arm64, replace `x64` with `arm64` in the above instructions.
+
+This will configure/update a systemd service called `certify-hub` running as user `certify`, with the main installed files under `/opt/certify-hub`. Settings will be stored under `/usr/share/certify`, by default the UI will be available at `http://localhost:8080`
+
+To then clean up the temporary install files:
+```
+rm -rf ./certify-hub*
+```
+
+##### Manual Install
+Alternatively, manually update and configure your install to your own preferences, you will need to run the executable `<install location>/Certify.HubService` to run the service and the user for the process will need to write to `/usr/share/certify`.
+
+### Post Install Steps
+The default configuration will make the service and UI available at `http://localhost:8080`, with the default username `admin` and default password `changeme!`.
+
+To use the service with https you can either [configure the service to use https](service.md) or reverse proxy the service from a webserver of your choice (Caddy, IIS, nginx, Apache etc and administer https on those as normal).
+
+:::note
+Do not install the Hub service where you also want to use Certify Certificate Manager (or Certify Management Agent) as they will share the same settings/databases via different services which could create confusion or conflicts and is not a supported configuration. 
+:::
+
+Suggested Configuration for multi-user access:
+- Create an internal DNS hostname for the service e.g. certify-hub.yourowndomain.com and point it at the internal IP of your server hosting the hub.
+- [Configure the service to use https](service.md)
+- Setup individual user accounts under Settings > Security > Users, and assign the roles required for each user (e.g. Administrator).
+
+## Certify Management Agent
+
+The following commands:
+- Download the latest version, ensuring any old download and old install files are removed if present
+- Extract the downloaded archive to the temporary ./certify-agent-install path
+- Runs the install script to install under /opt/certify-agent, and sets up the agent as a systemd service running as user `certify`.
+
+```
+rm ./certify-agent-linux-x64-latest.tar.gz -f
+wget https://certifytheweb.s3.amazonaws.com/downloads/archive/beta/agent/certify-agent-linux-x64-latest.tar.gz
+rm -rf ./certify-agent-install && mkdir -p ./certify-agent-install
+tar -xvf certify-agent-linux-x64-latest.tar.gz -C ./certify-agent-install
+sudo ./certify-agent-install/scripts/install-agent.sh
+```
+
+To then clean up the temporary install files:
+```
+rm -rf ./certify-agent*
+```

docs/hub/installation/windows.md

@@ -1,15 +1,10 @@
 ---
-title: Installing on Windows
+title: Install for Windows
 ---
 
-:::warning[feature under development]
-This feature is under development and documentation may refer to features and procedures that are not yet available.
-:::
 
-## Installing on Windows
-
-#### Install as a single service (UI and API)
-Install as a single combined management hub service is the simplest method with the least amount of configuration between components. This serves the Management Hub API, a backend certify-agent instance, and the web UI. Internally this is using the Kestrel web server which is part of Microsoft ASP.Net.
+#### Installing Certify Management Hub
+The management hub is installed as a single service which serves the Management Hub API, a backend certify-agent instance, and the web UI. Internally this is using the Kestrel web server which is part of Microsoft ASP.Net.
 
 You can download the latest **alpha test** version [7.0.2.23-alpha.07 : Released 2025/05/20](https://certifytheweb.s3.amazonaws.com/downloads/archive/hub/CertifyMgmtHubSetup_7.0.2.23-alpha.07.exe) - this is intended for test evaluation and not for production use, as subsequent updates may including breaking changes.
 

docs/hub/known-issues.md

@@ -26,15 +26,11 @@ Normally, when the system changes managed certificate or updates it status the c
 #### Loading time over slow connections
 The web app uses WebAssembly (WASM) and has a large application payload on initial load. Subsequent loads used cached resources.
 
-
-### Deployment Tasks
-The remote option (for SSH etc) is not currently enabled.
-
 ### Containers
 #### Data not persisted using containers
-The app will store settings in a combination of json files and SQLite DB files under `/usr/share/certify`. We will eventually offer the option to store some configuration in external databases such as postgres but the app does need to store some basic settings on file storage. In Docker etc this is achieved by mounting `/usr/share/certify` to persistant storage. You can override the app data path used by setting the `CERTIFY_APPDATA_PATH` environment variable to a preferred path. This path must be writeable by the non-root container user.
+The app will store settings in a combination of json files and SQLite DB files under `/usr/share/certify`. We will eventually offer the option to store some configuration in external databases such as postgres but the app does need to store some basic settings on file storage. In Docker etc this is achieved by mounting `/usr/share/certify` to persistent storage. You can override the app data path used by setting the `CERTIFY_APPDATA_PATH` environment variable to a preferred path. This path must be writeable by the non-root container user.
 
-Multiple instances of the Certify Agent or Management Hub service reading and writing the same SQLite database storage is not currently supported, so deployments should only ever have one active container. Continous backups/snapshots etc of your volume are *essential* for production environments because SQLite file based databases can, and do, fail.
+Multiple instances of the Certify Agent or Management Hub service reading and writing the same SQLite database storage is not currently supported, so deployments should only ever have one active container. Continuous backups/snapshots etc of your volume are *essential* for production environments because SQLite file based databases can, and do, fail.
 
 Note: We do not provide general support for how to use different container technology and you will likely need to know more about your choice of container deployment technology than we do, if you are using containers at all. Certify Management Hub is our first product that supports deployment to containers, so we expect growing pains.
 

docusaurus.config.js

@@ -6,9 +6,6 @@ module.exports = {
   favicon: 'img/favicon.ico',
   organizationName: 'webprofusion', // Usually your GitHub org/user name.
   projectName: 'certify-docs', // Usually your repo name.
-  future: {
-    experimental_faster: true,
-  },
   themeConfig: {
     algolia: {
       appId: 'YX7T7PF7BX',