Configuration

Starting Gruxi for the first time generates a default configuration, so you can get up and running quickly.

This basic configuration listens on port 80 for HTTP, port 443 for HTTPS, and port 8000 for the admin portal.

It also generates a single default site. It is served on ports 80 and 443 and serves the default Gruxi HTML from /www-default.

Automatic self-signed certificates for SSL/TLS

If no certificate is present, Gruxi automatically generates self-signed certificates for your domains. Replace them with valid certificates for your site hostnames.

Storage of configuration

Gruxi stores its configuration in a SQLite database located in /db. The file is named gruxi.db.

Getting started with configuration

By default, Gruxi listens on port 8000 for the admin portal, so you can reach it at https://<ip>:8000 (for example, https://localhost:8000). Once you open the admin portal, you will be prompted to log in.

Username: admin

The password is printed to the server output on first start and is only shown on the first run. If you missed it, run Gruxi again with the flag below to reset the admin password.

gruxi --reset-admin-password

Reloading configuration

When you make changes to the configuration (either via the admin portal or by editing the database directly, which is not recommended), Gruxi needs to reload the configuration to apply them. You can do this without restarting the server process by pressing the "Reload Configuration" button in the admin portal configuration editor.

WARNING

Reloading the configuration applies changes without restarting the server process. In some cases, it may temporarily disrupt service or require additional steps to fully take effect (for example, acquiring TLS certificates after startup).

Next step

After you have logged in to the admin portal, you will have access to change the configuration. The first thing to consider is the bindings Gruxi should listen on.