If you navigate to your sellery instance, and request any file, you will instantly be prompted for a password.
Once entered (and correct), your browser will set a cookie with a session id. This session will remain active for (by default) 10 minutes when inactive.
It will only renew when requesting another file.
With this cookie set, you can freely browse your webroot as if it was hosted by a regular, public webserver.
Sellery can be functionally customized by modifying the config file, and optically customized by modifying
the `authenticate.html` file, which is the login page. Anything else (like the login-failed page) is a statically
served string. Serving a custom page would require a bit, but not much, more work.
Do note that just deleting key-value pairs from the config file will most likely result in the server just crashing :).
## Telemetry and logging
### Telemetry
Sellery, in of itself, records no telemetry what-so-ever. What node.js, or any of the installed packages, do in the background,
i have no idea. Probably nothing, but don't quote me on that.
### Logging
Sellery **only** logs failed login attempts. This is important for the users privacy, so they can check if
someone's trying to break into their instance. This can be fairly easily disabled though.
Again, i have no idea if node.js's https-server logs anything in the background. I don't think so.
## How to generate your ssl pem files (self-signed):
