Update container instructions

Author: webprofusion-chrisc

docs/hub/installation/containers.md

@@ -9,33 +9,43 @@ Using [docker](https://docker.com/) is a way to quickly try out *Certify Managem
 
 :::
 
-A key thing to know about running apps in docker is that the container should be considered temporary (to be recreated later), so data should not be stored only within the container itself. To host the app in docker properly, you need to specify a persistent data volume to store configuration data (which hy default is under `/usr/share/certify`).
+A key thing to know about running apps in docker is that the container should be considered temporary (to be recreated later), so data should not be stored only within the container itself. To host the app in docker properly, you need to specify a persistent data volume to store configuration data (which by default is under `/usr/share/certify`).
 
-#### Quick Start using Docker Compose
+#### Quick Start using Docker Compose (recommended)
 Save this file as `docker-compose.yaml`
 
 ```yaml
 name: certify-management-hub
 services:
   certify-hubservice:
     image: docker.io/certifytheweb/management-hub:latest
-    hostname: certify-hubservice
     ports:
       - "8080:8080"
     volumes:
       - certifydata:/usr/share/certify/
+    restart: unless-stopped
 volumes:
   certifydata:
 ```
 
-Then from the same path, run `docker compose up -d` to start the container.
+Then from the same path, run `docker compose up -d` to start/restart the container. 
+
+##### Upgrading
+
+Using the latest version with docker compose is quick and easy:
+- Fetch the latest update with `docker pull certifytheweb/management-hub:latest` 
+- then restart your container (from the path where your above `docker-compose.yaml` is kept): `docker compose up -d`
 
 #### Quick Start directly with Docker Run
 Alternatively, to quickly try it out without using docker compose:
 
-`docker run -v /local/path/to/data:/usr/share/certify -p HOST_PORT:8080 docker.io/certifytheweb/management-hub:latest` 
+`docker run --name certify-management-hub -d -v /local/path/to/data:/usr/share/certify -p HOST_PORT:8080 --restart unless-stopped docker.io/certifytheweb/management-hub:latest` 
+
+e.g. `docker run --name certify-management-hub -d -v C:\temp\certifydata -p 8080:8080 --restart unless-stopped docker.io/certifytheweb/management-hub:latest`
+
+##### Upgrading
 
-e.g. `docker run -v C:\temp\certifydata -p HOST_PORT:8080 docker.io/certifytheweb/management-hub:latest`
+- Fetch the latest update with `docker pull certifytheweb/management-hub:latest` then recreate your container.
 
 ### Other common container environments
 

docs/hub/known-issues.md

@@ -23,10 +23,6 @@ The web app uses WebAssembly (WASM) and has a large application payload on initi
 #### Errors when trying to login
 The UI needs to know the URL of the API it should talk to. This is configured by default to https://localhost:44361 or http://localhosts:808 when running from docker. The setting is changed for all users by editing wwwroot/appsettings.json or you can temporarily change the URL in the login page by clicking the Settings gear icon and setting the correct URL for your installation.
 
-### DNS Providers
-#### Posh-ACME based DNS providers not working
-This is a known issue and is being worked on.
-
 ### 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 teh 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.