I think it would be a good idea to at least update the installation guide, or better yet include Caddy and a basic caddyfile in the distribution
For an
- intranet Manager Server at say IP 192.168.1.10
- the default Manager local server installation on port 8080
- Caddy in an accessible directory, for example the same as ManagerServer
Create a file named “caddyfile” (with no extension) in a text editor with the contents
192.168.1.10, localhost, 127.0.0.1
reverse_proxy 127.0.0.1:8080
Copy the above Caddyfile and caddyfile.exe into the same directory as ManagerServer
To manually run the Manager server
- Start Manager server as per the guide
- Start Caddy by opening a command prompt, cd to the directory caddy is in if required, then type the command
caddy run
or
caddy start
The latter runs it in background, requires a Caddy stop to stop it or Caddy reload to update the configuration
If your self hosted Manager server is to be accessible form the internet / replace the first line in the caddyfile with your domain name.
Manager server can then be accessed over your local intranet from a web browsers. In the above example
http://192.168.1.10:80
will redirect to
https://192.168.1.10:443
When you first browse to that location, your browser will give an error indicating the authenticity could not be verified, consistent with caddy generating a self signed certificate.
Either accept the exception or manually instal the certificate onto the computer/browser you are using to access Manager. The certificate is located on the computer caddy is running on in the directory C:\Users<Your Name>\AppData\Roaming\caddy\