Restrict configuration to config file

This drops also the -d flag and the database/user config option.

The -d flag used to override specific parts of the config file. This is
just confusing behaviour. Instead a new config/debug.json file is
introduced with useful default values.

Instead of configuring the database user via the database/user entry in
the config file, the user is determined from the Linux user of the
server process. This enforces that a database user with the same name as
the Linux user is configured which is already described in the README.

0 files changed, 0 insertions, 0 deletions