getlino configure command¶
- getlino configure¶
If you run
getlino configure as root (using
sudo), it will
potentially also install system packages and create or overwrite system-wide
configuration files. Otherwise it will install Lino into a virtualenv.
If you want Lino to install into an existing virtualenv, you should
activate it before running
getlino configure in order to use it as your
getlino configure (unless invoked with --batch) asks a lot of
questions, one question for each server configuration option. Read the docs
below for more explanations. You can answer ENTER to each question if you don't
getlino configure creates or reads and updates a configuration file where
it stores your answers. Depending on whether you are root, the configuration
file will be either
If you specify
--batch, every option gets its default value, which you
may override by specifying command-line arguments. Use this option only when you
know what you want (e.g. in a Dockerfile).
getlino configure as root, you may want to run it once more
without being root, because only then it will also write a
.bash_aliases file in your home directory.
Run-time behaviour options:
Which web server to use on this production server. This can be "nginx", "apache" or empty. When not given, getlino will not setup any web server configuration.
You should not change this value when there is already at least one Lino site on this server.
Run in batch mode, i.e. without asking any questions. Assume yes to all questions.
Server configuration options
Full path to a shared virtualenv to be used by all new sites.
If this is empty, every new site will get its own virgin environment.
When not running as root, the default value is taken from the
VIRTUAL_ENVenvironment value (all your sites will use a same environment).
When configure is running as root, the default value is an empty string (you usually don't want a shared virtualenv on a production site). Except when
--cloneis also given. In this case getlino stores the current
VIRTUAL_ENVenvironment value as default value (or raises an error when no virtualenv is activated).
Whether to install development tools (used to build docs and run tests).
The root directory for Lino's log files on this server. Each new site will get its entry below that directory.
The root directory for backups on this server. Each new site will get its entry below that directory. Used e.g. by
The root directory for sites on this server.
New sites will get created below that directory (with another level named by
Prefix for local server-wide importable packages.
Relative directory or symbolic link to the virtualenv.
Relative directory or symbolic link to repositories.
Fully qualified domain name of this server. Default is 'localhost'.
Default settings for new sites
Which front end (
default_ui) to use on new sites.
Default value for
languagesof new sites.
Whether new sites should have a
linod.shscript which runs the
When running as root, this will also add a
supervisorconfiguration file which runs the
Default value is 'mysql' when running as root or 'sqlite3' otherwise.
A shared database username to use for all sites on this server.
If this is set, you must also set
Used during development and testing when you prefer to have a single database user for all databases. For security reasons these options should not be used on a production server.
The port to use for connecting to the database server when
Whether this server provides LibreOffice service needed by sites that use
Whether new sites should have webdav.
Whether this server provides an LDAP service. Not tested.
Whether this server provides secure http.
This option will cause getlino to install certbot.
When you use this option, you must have your domain name (
--server-domain) registered so that it points to the server. If your server has a dynamic IP address, you may use some dynamic DNS service like FreedomBox or dynu.com.