Managing Settings
From the Backend#
The Settings menu in Manifold's backend allows non-technical users to customize their instance. Settings are stored in Manifold's database, and can be viewed from an API console session using Settings.instance.
To access settings, you must be logged in as an admin user. Each of the available settings are described in more detail in the subpages of this page.
From the Environment#
tip
To learn how to manage environment variables from a package installation of Manifold, see this section of our documentation.
When Manifold's API service starts, it is possible to set any of Manifold's setting through an environment variable. This process happens once, when the application starts. To read settings from the environment, the following environment variable must be set:
If that variable is present, Manifold will map environment variables that begin with MANIFOLD_SETTING_ to the corresponding setting value in the database. On startup, the settings record in the database will be updated with the value from the environment.
info
The authoritative settings record in the database is updated from the environment when Manifold starts up. This means that you could load a setting from the environment, then change it in the web interface. The next time Manifold is restarted, the value from the environment will overwrite the updated value. Be aware of this caveat if you manage settings from the environment.
While most setting environment variables are straight-forward, there is one that is unique:
This variable allows you to refer to a google cloud service account json key. When Manifold boots up, it will parse this key and assign the various values to the correct settings. This is useful if you're deploying Manifold to a Google Cloud environment and need to automatically provision and provide Manifold with a service account as part of that process.
As of Manifold v6, the following settings can be set from the environment: