You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/hub/installation/windows.md
+3-10Lines changed: 3 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,20 +13,13 @@ There are two ways to install Certify Management Hub directly on Windows (if not
13
13
#### Install as a single service
14
14
Install as a single combined management hub service, this 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.
15
15
16
-
You can download the latest **alpha test** version [7.0.0.16-alpha.03 : Released 2025/05/03](https://certifytheweb.s3.amazonaws.com/downloads/archive/CertifyMgmtHubSetup_V7.0.0-alpha.03.exe) - this is intended for test evaluation and not for production use, as subsequent updates may including breaking changes.
16
+
You can download the latest **alpha test** version [7.0.1.19-alpha.05 : Released 2025/05/08](https://certifytheweb.s3.amazonaws.com/downloads/archive/hub/CertifyMgmtHubSetup_7.0.1.19-alpha.05.exe) - this is intended for test evaluation and not for production use, as subsequent updates may including breaking changes.
17
17
18
-
The current default configuration will make the service and UI available at `http://localhost:8080` and you will need to set the API endpoint (the same URL) in the login UI.
18
+
The current default configuration will make the service and UI available at `http://localhost:8080`
19
19
20
20
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).
21
21
22
-
### Install as multiple services, possibly on different servers etc.
23
-
- Or, if you need more control over how things are organized, install the components separately:
24
-
-**The Management Hub API**. This the provides aggregated services to talk to one or more *Certify Agent* or *Certify Certificate Manager* instances. The hub needs to know the details of the certify agent service it will use for backend storage services etc.
25
-
- The **Certify Agent** service. This provides backend storage and certificate management services. The agent needs to know the final URL of the Management Hub API to talk to it.
26
-
- Serve the **Web UI** via IIS or other web server. The `/wwwwroot/appsettings.json` file of the web app needs to be configured with the Management Hub API url.
27
-
28
-
The Management Hub API and Certify Agent service both need to be configured to know how to talk to each other, and this is often the most complex part to get right.
29
-
22
+
Do not install the Hub service where you also want to use Certify Certificate Manager as they will share the same settings/databases via different services which could create confusion or conflicts and is not a supported configuration. You can however upgrade a Certify Certificate Manager install to be a hub: uninstall Certify Certificate Manager (the desktop app_ first, install Certify Management Hub, then use the hub to administer your certificates as normal.
30
23
31
24
### Settings are preserved between installs/upgrades
32
25
On Windows your settings are preserved in `%PROGRAMDATA%\certify`. For most users, this is `C:\ProgramData\certify`. Uninstalling the app or installing a new version does not remove the files stored here. We recommend including this location in your regular backup procedure.
0 commit comments