World Overview of Conservation Approaches and Technologies

• POSTGRES_USER: User for postgres database
• POSTGRES_PASSWORD: Password for postgres database
• DJANGO_ADMIN_URL: URL of Django admin interface
• DJANGO_SETTINGS_MODULE: Python path syntax to django settings module
• DJANGO_SECRET_KEY: A secret key for a particular Django installation
• DJANGO_ALLOWED_HOSTS: A list of strings representing the host/domain names that this Django site can serve
• DJANGO_ACCOUNT_ALLOW_REGISTRATION: Allow registration of new users (default True)
• DJANGO_SENTRY_DSN: DSN for Sentry error tracking
• WAGTAILSEARCH_BACKEND: 'db' for regular Psql, 'elasticsearch' or 'elasticsearch2' for ES1 or 2.
• ELASTICSEARCH_URL: Elasticsearch URL
• NEWSLETTER_API_KEY: Mailchimp API Key
• NEWSLETTER_LIST_ID: Mailchimp List ID
• DJANGO_EMAIL_HOST: The host to use for sending email
• DJANGO_EMAIL_HOST_USER: Username to use for the SMTP server
• DJANGO_EMAIL_HOST_PASSWORD: Password to use for the SMTP server
• DJANGO_EMAIL_PORT: Port to use for the SMTP server
• DJANGO_EMAIL_USE_TLS: Whether to use a TLS (secure) connection when talking to the SMTP server
• DJANGO_EMAIL_USE_SSL: Whether to use an implicit TLS (secure) connection when talking to the SMTP server
• DJANGO_DEFAULT_FROM_EMAIL: Default email address to use for various automated correspondence from the site manager(s)
• DJANGO_SERVER_EMAIL: The email address that error messages come from

• Python >= 3.0
• Elasticsearch/Tika

1. Create and activate virtualenv (optional)

2. Install requirements

$ pip install -r requirements/local.txt
or for production:
$ pip install -r requirements/production.txt

3. Install database (Postgres)

$ psql -d database_name -c "create role <USER> with password <PASSWORD>";
$ psql -d database_name -c "create database <DATABASE> with owner <USER>";
$ python manage.py migrate

4. Copy „env.example“ to „.env“, adapt settings
5. Collect static files (required only for deployment server)

$ python manage.py collectstatic --no-input

5. Run server

$ python manage.py runserver

Deployment requires SSH access to the deployment server without password using SSH keychain. We recommend using fabric to pull code, update new requirements, collect static files, compile translations and migrate the database.

# for development:
$ fab development deploy
# for staging:
$ fab staging deploy
# for production:
$ fab production deploy

$ pip install -rU requirements.txt

The project uses mailchimp: https://mailchimp.com/

https://login.mailchimp.com/signup Please follow their instructions on how to setup an account and create a list. Both the api key and list id need to be set in order for the integration to work. (please see settings section for respective environment variable setup)

There is a newsletter management interface to create a filtered list of users, that can be pasted into the mailchimp list.

1. Go to https://www.wocat.net/newsletter/management/
2. Select filters and copy output to clipboard
3. Go to mailchimp list, under „Add contacts“ select „Import contacts“
4. Select „Copy/paste from file“ and paste from clipboard
5. Match columns and import

To synchronize the newsletter flag upon unsubscription via newsletter email link a webhook needs to be registered. http://kb.mailchimp.com/integrations/api-integrations/how-to-set-up-webhooks

1. Go to mailchimp list
2. Under „Settings“ select „Webhooks“
3. Select „Create new webhook“ and paste URL: https://www.wocat.net/newsletter/unsubscribe/
4. Select only the checkbox for „Unsubscribes“ and save

To use Elasticsearch as a search-backend, it suffices to just set it up (through your distributions package management) and change the WAGTAILSEARCH_BACKEND-variable accordinly. As of writing this, a feature for indexing PDFs and other documents has not made it into upstream wagtail (wagtail/wagtail#3028) . Once this feature is merged, we can retroactively index all uploaded documents. (The index engine for ElasticSearch is based on [Tika](https://tika.apache.org/) and can therefore index anything Tika can.)

• To create a normal user account, just go to Sign Up and fill out the form. Once you submit it, you'll see a "Verify Your E-mail Address" page. Go to your console to see a simulated email verification message. Copy the link into your browser. Now the user's email should be verified and ready to go.

• To create an superuser account, use this command:

  $ python manage.py createsuperuser
  

For convenience, you can keep your normal user logged in on Chrome and your superuser logged in on Firefox (or similar), so that you can see how the site behaves for both kinds of users.

To import users from CSV use this command:

$ python manage.py import_users_data /path/to/institutions.csv /path/to/users.csv

The CSV file specs are (check samples files in /import folder)

• encoding: UTF-8
• delimiter: ";"
• quoting:
• escape character:

Attention: Please check before the import again whether the data basis is clean, especially regarding the institutes!

After the final import of the users, they are informed by e-mail that they have to re-assign their password. This mail to the user contains a personal link, which allows you to set a password directly (without having to go through the password-forgotten function). The mail is therefore sent by the CMS, implemented here for a command which triggers the emails:

$ python manage.py send_user_password_reset_links

$ ./manage.py update_index [--backend <backend name>]

This command rebuilds the search index from scratch. It is only required when using Elasticsearch.

It is recommended to run this command once a week and at the following times:

whenever any pages have been created through a script (after an import, for example) whenever any changes have been made to models or search configuration The search may not return any results while this command is running, so avoid running it at peak times.

$ python manage.py search_garbage_collect

Wagtail keeps a log of search queries that are popular on your website. On high traffic websites, this log may get big and you may want to clean out old search queries. This command cleans out all search query logs that are more than one week old (or a number of days configurable through the WAGTAILSEARCH_HITS_MAX_AGE setting).

The style sheets are written in LESS. They will be compiled to a single CSS file by $ lessc while running Fabric. See compile_less() in fabfile.py.

There are two kinds of translations:

• CMS translations: Can be added directly through the CMS admin interface by editing the translation page.
• Source code translation: All other translations (like forms or captions) are handled by Django translation, translation happens on Transifex (https://www.transifex.com/university-of-bern-cde/wocat-website/).

Preparation:

• Add new language to LANGUAGES in config/settings/common.py
• Define a link (e.g. de_link) for the new language in wocat/cms/translation.py, also add field FilterField in search_fields.

Source code translation - Create po file:

• Add new translations to PO file (e.g. DE for german)

  $ python manage.py makemessages -l <LANGUAGE>

CMS translation - Copy page tree:

• To copy the entire page tree into a new language, use the following management command:

  Note

  On WOCAT Live, translation pages are currently deactivated. Once page tree is copied, remove feature toggle FEATURE_SHOW_TRANSLATIONS.

  python manage.py create_translation_tree

  This command can also be used to copy a single page within the tree (just modify the defaults).

Source code translation:

• To update translations (happening on Transifex), use:

  python manage.py makemessages

• To use translations, use the following management command:

  python manage.py compilemessages

  This step is executed by fabric during deploy.

Sentry is an error logging aggregator service. You can sign up for a free account at http://getsentry.com or download and host it yourself. The system is setup with reasonable defaults, including 404 logging and integration with the WSGI application.

You must set the DSN url in production.