Flawed installation documentation leads to new questions

Support
1

My version of HedgeDoc is: 1.10.3

What I expected to happen:

Easily find configuration text to host Hedgedoc immediately on a public IP with no proxy.

What actually happened:

The information to host Hedgedoc on a public IP with no proxy does not exist.

I already tried:

I looked in the official Hedgedoc installation documentation.

Request:

Please give an example (similar to the localhost example) of how to run Hedgedoc (serve on a public IP) for the first time on a new VSP with no webserver or proxy installed.

Note:

If Socket.io or other Hedgedoc dependencies require an external server or proxy, then let’s please correct the documentation (‘Requirements on your server’ at the very top) to reflect that.

3

It appears that only one of the lines of the Hedgedoc configuration shown in the installation document requires changing, in order to directly serve without any other server or proxy:

< - CMD_DOMAIN=localhost

  - CMD_DOMAIN=<put-your-ip-domain-hostname-here>

…after which you can start Hedgedoc with $ docker-compose up and browse to it (type the configured domain in the URL bar) from a different computer. You must type :3000 at the end of the URL bar.

This causes Hedgedoc to work as expected, but it doesn’t help anybody who is trying to use Hedgedoc together with another web server or proxy.