Configure the Application for Development or Production

Finally, create a file dissemin/settings/ with this content:

# Development settings
from .dev import *
# Production settings.
from .prod import *
# Pick only one.

For most of the settings we refer to the Django documentation.


Dissemin comes with a predefined log system. You can change the settings in dissemin/settings/ and change the default log level for production and development in the corresponding files. When using Dissemin from the shell with ./manage shell you can set the log level for console output as environment variable with:


When using in production make sure that apache collects all your log message. Alternatively you can send them to a separate file by changing log settings.


Dissemin uses Sentry to monitor severe errors. To enable Sentry, set the SENTRY_DSN.


You can either use production ORCID or its sandbox. The main difference is the registration process.

You are not forced to configure ORCID to work on Dissemin, just create a super user and use it!


On your ORCID account got to Developer Tools and register an API key. As a redirection URL you give the URL to your installation.

Set ORCID_BASE_DOMAIN to in the Dissemin settings.

On the admin surface got to Social Authentication, set the provider to and enter the required data.

Now you can authenticate with ORCID.


Create an account on Sandbox ORCID.

Go to Developer Tools, verify your mail using Mailinator <>. You must not choose a different provider.

Set up a redirection URI to be localhost:8080 (supposed to be where your Dissemin instance server is running).

Now proceed as in Production, but with