Artemis configuration happens at two stages: before installation (via shell variables thatDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/artemis-development-group/artemis/llms.txt
Use this file to discover all available pages before exploring further.
install.cfg reads) and after installation (by editing the generated *.update files and regenerating *.ini files). This page covers both, starting with the variables you need before you run artemis.sh.
Pre-install variables
These variables are defined inartemis/install/install.cfg and can be overridden as environment variables passed to the install script. For example:
| Variable | Default | Description |
|---|---|---|
ARTEMIS_USER | $SUDO_USER | The system user that owns and runs the Artemis processes. Must not be root. Required — the script exits if this is unset. |
ARTEMIS_GROUP | nogroup | The system group that Artemis processes run as. Must already exist on the system. |
ARTEMIS_HOME | /home/$ARTEMIS_USER | Base directory for the install. Used to derive ARTEMIS_SRC if that is not set explicitly. |
ARTEMIS_SRC | $ARTEMIS_HOME/src | Directory where repositories are cloned. The installer creates this directory if it does not exist. |
ARTEMIS_DOMAIN | artemis.local | The domain name Artemis will be served from. Must contain a . — browsers do not set cookies for dotless hostnames. An IP address works if no domain is available. |
ARTEMIS_PLUGINS | about gold | Space-separated list of plugin names to install. Each plugin must be a directory present in $ARTEMIS_SRC that follows the plugin naming convention. |
ARTEMIS_USER has no default when you run the script directly as root (i.e., when $SUDO_USER is empty). Create a dedicated user and set this variable explicitly:Default plugins
The default value ofARTEMIS_PLUGINS installs two plugins:
about— Provides the/aboutpage and related informational routes for the instance.gold— Adds the Gold subscription and gilding system, including the/goldpurchase flow and/api/v1/gold/API endpoints.
ARTEMIS_PLUGINS to an empty string or list only the plugins you want:
ARTEMIS_PLUGINS but whose directories are not found in $ARTEMIS_SRC are silently skipped at install time.
INI files and run.ini
The installer generates configuration files in/home/src/artemis/r2/:
| File | Purpose |
|---|---|
development.update | Editable source file for development settings. Run make ini after editing to regenerate development.ini. |
development.ini | Generated Paste configuration for development. Has debug = true, ads disabled, captcha disabled, and rate limiting disabled. |
production.ini | Generated Paste configuration for production. Has debug = false and all safety features enabled. |
run.ini | Symlink pointing to either development.ini or production.ini. The app always reads run.ini. |
run.ini pointing to development.ini by default. Switch to production mode by updating the symlink:
development.update reference
Thedevelopment.update file is generated by the installer with sensible defaults. Edit it to change domain, plugin list, or any [DEFAULT] INI key, then regenerate:
development.update looks like this:
Environment variables set at runtime
The installer writes/etc/default/artemis with these environment variables, which are sourced by init scripts and background job consumers: