Package containing the main project settings.
Distro Tracker settings
The settings are created dynamically by first importing defaults
distro_tracker.project.settings.defaults and then
distro_tracker.project.settings.local (or from
distro_tracker.project.settings.selected if the latter
has not been created by the administrator). The test suite
is special cased and doesn’t use any of those, instead it uses
Default Django settings for the Distro Tracker project.
Most settings are documented in this file and they are initialized to some reasonable default values when possible. They will be extended (and possibly overridden) by settings from the other modules in this package depending on the setup selected by the administrator. You likely won’t have to modify that file.
You should instead create local.py to put your site-specific settings (use local.py.sample as template).
Here are the most important settings:
The fully qualified domain name of the distro-tracker installation. It should be a service-specific DNS entry like “tracker.example.com”. Defaults to the FQDN of the machine which might not be adequate.
The directory where distro-tracker will hold its data. The directory is further sub-divided in multiple directories for specific use cases (e.g. cache, keyring, static, media, logs, templates, etc.). Defaults to the “data” sub-directory in the distro-tracker base directory (where the code lives).
Some settings have default values which are computed dynamically from other settings. Those settings can also be overridden. Here’s the list of those settings.
The name of the vendor. Equivalent to the Vendor field of an /etc/dpkg/origins file. Default value computed from the domain name of
The URL of the vendor. Equivalent to the Vendor-URL field of an /etc/dpkg/origins file. Default value computed as “www.” + the domain name of
Absolute path to the directory static files should be collected to. Don’t put anything in this directory yourself; store your static files in apps’ “static/” subdirectories and in STATICFILES_DIRS. Defaults to the “static” sub-directory of
Absolute filesystem path to the directory that will hold user-uploaded files. Defaults to the “media” sub-directory of
This directory is used to store the locally cached resources. Any Distro Tracker app should be able to use this directory to store its caches. For example, it is used to store the APT cache of repository information and the cache of retrieved Web resources. Defaults to the “cache” sub-directory of
This directory should contain a gpg.conf listing the GPG keyrings of known public keys. It’s used to identify authors of package uploads. Defaults to the “keyring” sub-directory of py:data:DISTRO_TRACKER_DATA_PATH.
This directory will hold log files generated by distro-tracker. Defaults to the “logs” sub-directory of py:data:DISTRO_TRACKER_DATA_PATH.
This directory is used as a mailbox in the Maildir format. All incoming mails are stored here. Defaults to the “maildir” sub-directory of py:data:DISTRO_TRACKER_DATA_PATH.
This directory can hold custom templates that will override the templates supplied by distro-tracker. Defaults to the “templates” sub-directory of py:data:DISTRO_TRACKER_DATA_PATH.
The email address which is to receive control emails. It does not necessarily have to be in the same domain as specified in
DISTRO_TRACKER_FQDN. Defaults to “control@” +
The email address which is to receive contact emails. It does not necessarily have to be in the same domain as specified in
DISTRO_TRACKER_FQDN. Defaults to “owner@” +
The email address which is to be used as the sender address when no bounce processing should happen. It does not necessarily have to be in the same domain as specified in
DISTRO_TRACKER_FQDN. Defaults to “bounces@” +
The email address which should receive bounces that are likely the result of incoming spam.
This file is the trusted.gpg main file to hand out to APT
This directory is trusted.gpg.d directory to hand out to APT
The number of days to tolerate bounced messages for subscribers.
The number of errors after which the processing of a command email stops.
The number of days a command confirmation key should be valid.
The maximum number of news to include in the news panel of a package page
The maximum number of RSS news items to include in the news feed
A list of extra headers to include when rendering an email news item. See:
The maximum size that the
distro_tracker.core.utils.packages.AptCacheshould consume for all of its cached source files, given in bytes.
The path to the CA bundle used to verify TLS connections. Defaults to the system-wide CA bundle.
Whether we accept firstname.lastname@example.org as valid emails to dispatch to the foo package
Whether we include a captcha check on the new user registration form
Dynamically generate some default settings.
There are many settings whose default value depends on another setting. They are defined in the _COMPUTE_DEFAULT_SETTINGS dict with a function that evaluates them.
Return the name of the Package Tracker instance.
This file has appropriate settings for running in production.
When running in production, selected.py should point to this file.
Appropriate settings to run during development.
When running in development mode, selected.py should point to this file.
Appropriate settings to run the test suite.