gmid can be run in two different “modes”:
To run gmid in the “configless” mode, just type:
$ gmid path/to/dir
gmid will then generate a certificate inside ~/.local/share/gmid and serve the given directory locally.
To host a Gemini capsule you need to run gmid in “daemon” mode.
To run gmid in daemon mode a configuration file is needed. The format of the configuration file is described in the manpage and is quite flexible, but something like the following should be enough to start:
# /etc/gmid.conf
server "example.com" {
cert "/etc/ssl/example.com.pem"
key "/etc/ssl/private/example.com/key"
# path to the root directory of your capsule
root "/var/gemini/example.com"
}
A certificate is needed for the capsule. Generate one for e.g. using contrib/gencert:
$ ./contrib/gencert example.com
Generating a 4096 bit RSA private key
.................................................++++
..........++++
writing new private key to './example.com.key'
-----
Generated files:
./example.com.pem : certificate
./example.com.key : private key
Move ‘example.com.pem’ and ‘example.com.key’ to a safe place and double check that the ‘cert’ and ‘key’ options in the configuration points to these files.
For example, save them in ‘/etc/ssl/’ (as root)
# mkdir -p /etc/ssl/private # chown 700 /etc/ssl/private # mv example.com.pem /etc/ssl/ # mv example.com.key /etc/ssl/private/
Make sure that the ‘cert’ and ‘key’ options in the configuration file points to these files.
Then running gmid is as easy as
$ gmid -c /etc/gmid.conf
Congratulations, your capsule is online!
gmid employs various techniques to prevent the damage caused by bugs, but some steps needs to be done manually.
If gmid was installed from your distribution package manager, chance are that it already does all of this and is also providing a service to run gmid automatically (e.g. a rc script, a systemd unit file …) Otherwise, it’s heavily suggested to create at least a dedicated user.
Ideally, gmid should be started as root and drop privileges to a local user. This way, the certificates can be readable only by root. For example, on GNU/linux systems a ‘gmid’ user can be created with:
# useradd --system --no-create-home -s /bin/nologin -c "gmid Gemini server" gmid
Please consult your OS documentation for more information on the matter.
The configuration then needs to be adjusted to include the ‘user’ directive at the top:
# /etc/gmid.conf
user "gmid"
server "example.com" { … }
gmid then needs to be started with root privileges, but will then switch to the provided user automatically. If by accident the ‘user’ option is omitted and gmid is running as root, it will complain loudly in the logs.
It’s a common practice for system daemons to chroot themselves into a directory. From here on I’ll assume /var/gemini, but it can be any directory.
A chroot on UNIX-like OS is an operation that changes the “apparent” root directory (i.e. the “/”) from the current process and its child. Think of it like imprisoning a process into a directory and never letting it escape until it terminates.
Using a chroot may complicate the use of CGI scripts, because then all the dependencies of the scripts (sh, perl, libraries…) need to be installed inside the chroot too. For this very reason gmid supports FastCGI.
The chroot feature requires a dedicate user, see the previous section.
To chroot gmid inside a directory, use the ‘chroot’ directive in the configuration file:
# /etc/gmid.conf user "gmid" # the given directory, /var/gemini in this case, must exists. chroot "/var/gemini"
Note that once ‘chroot’ is in place, every ‘root’ directive is implicitly relative to the chroot, but ‘cert’ and ‘key’ aren’t!
For example, given the following configuration:
# /etc/gmid.conf
user "gmid"
chroot "/var/gemini"
server "example.com" {
cert "/etc/ssl/example.com.pem"
key "/etc/ssl/example.com.key"
root "/example.com"
}
The certificate and the key path are the specified ones, but the root directory of the virtual host is actually “/var/gemini/example.com/”.