The configuration file generated in the Setup step consists of the following configuration sections:
The configuration file uses the standard .ini format that follows this structure:
[section_name] setting.name = value
The settings in this section configure the Experiment Support System itself.
To work correctly, they must all be specified within the
section of the configuration file.
The title to use for the Experiment Support System. Change this to integrate the system into a site-specific branding.
Default: Experiment Support System
- The SQLAlchemy database connection URL. Consult the SQLAlchemy connection string documentation to find the correct format for the database and database library you are using.
- The host-name of the SMTP server to use for sending e-mails. If this setting is not specified then non of the e-mail related functions in the Experiment Support System will be enabled.
The settings in this section specify how the user sessions are managed. For details on the available settings, consult the beaker documentation. In most cases you will only want to change the beaker.session.key setting.
The directory used for locking.
The type of session storage to use. By default uses cookie-based sessions.
The key to use for session access. With cookie-based sessions this is the name of the cookie to use.
- Encryption key to use to ensure cookie-based sessions are harder to manipulate. The key is automatically and semi-randomly generated when the configuration is created.
- Validation key to use to test that cookie-based sessions have not been manipulated. The key is automatically and semi-randomly generated when the configuration is created.
The settings in this section are set for a production deployment and should not be changed in a production environment.
Whether to automatically reload HTML templates when they are updated.
Whether to provide detailed debug information for the authorization process.
Whether to provide detailed debug information for URLs that are not handled by the Experiment Support System.
Whether to provide detailed debug information on the URL processing functions.
Whether to provide detailed debug information for errors in the HTML templates.
The default locale to use.
Any additional components to load on application startup. By default the Pyramid Transaction Management component is loaded. For debugging add
pyramid_debugtoolbarto this setting. This will allow arbitrary access to everything in the application. Do not include on a production system.
This section configures the default built-in application server, which is
mainly designed for use in development and testing. For production scenarios
consult the Deployment documentation. These settings must all be
specified with in the
The application server entry point to use.
The host to listen at for connections.
The port to listen at for connections.