Hedgedoc: Difference between revisions
m →Nginx reverse proxy (virtualization host/server with public IPv4): Remove link to immaginary example |
Finished a unfinished sentence about disabling guest users. |
||
| Line 15: | Line 15: | ||
In a setup with a VM/internal machine on 192.168.1.100 and a public accessible reverse proxy/VM host running the „hedgedoc.example.com“ domain you will probably use a setup like this: | In a setup with a VM/internal machine on 192.168.1.100 and a public accessible reverse proxy/VM host running the „hedgedoc.example.com“ domain you will probably use a setup like this: | ||
=== Hedgedoc server (virtual machine/internal server) === | === Hedgedoc server (virtual machine/internal server) === | ||
Hedgedoc does not need more than a handful options for configuration. | Hedgedoc does not need more than a handful options for configuration. | ||
<syntaxhighlight lang="nixos"> | <syntaxhighlight lang="nixos"> | ||
networking.firewall = { | networking.firewall = { | ||
| Line 33: | Line 33: | ||
</syntaxhighlight> | </syntaxhighlight> | ||
Notice: With this configuration hedgedoc is freely usable without authentification. In the current version of hedgedoc there is no admin backend. To have control about the users you can restrict usage by disabling self registration (allowEmailRegister) and guest access (allowAnonymous): Set both to false in services.hedgedoc.settings. | |||
=== Nginx reverse proxy (virtualization host/server with public IPv4) === | === Nginx reverse proxy (virtualization host/server with public IPv4) === | ||
The reverse proxy for <code><nowiki>https://hedgedoc.example.com</nowiki></code> with an internal hedgedoc server running on 192.168.1.100 will work with this: | The reverse proxy for <code><nowiki>https://hedgedoc.example.com</nowiki></code> with an internal hedgedoc server running on 192.168.1.100 will work with this: | ||