Merengue specific settings

Available settings

Here’s a full list of all available merengue settings. All these settings are defined in merengue/settings.py and can be overriden in your project settings.

HTTP_STATUS_CODE_TEMPLATES

Default: {403: ‘403.html’, 404: ‘404.html’,}

When a HTTP status code (not 500) is found in response, you may want to use an especific template to render. This is needed in example to catch all permission error code (403 error).

SITE_FIXTURES

Default: {} (Empty dictionary)

A dictionary mapping with fixtures to load for every application It will executed after migrating (with south) models for every application. Example:

SITE_FIXTURES = {
    'blog': ('blogs_data.xml', )
    'news': ('news_data.xml', 'news_users.json', )
}

In this example, after migrate 'news' application Merengue will load news_data.xml and news_users.json, located in one of settings.FIXTURE_DIRS.

MERENGUE_URLS_PREFIX

Default: cms

It will be the prefix for all URLs managed by merengue. Those URLs are defined in merengue/urls.py file.

In your project urls.py file, merengue URLs are included as follows:

# merengue URLs
(r'^%s/' % settings.MERENGUE_URLS_PREFIX, include('merengue.urls')),

You can override this settings if you prefer other prefix than cms.

URL_DEFAULT_LANG

Default: The LANGUAGE_CODE value

It will say to Merengue what URL will be used in internazionalized URLs.

For example, if you declare a in a plugin config.py file, a url_prefixes like that:

class PluginConfig(Plugin):
    # ... stuff
    url_prefixes = (
        ({'en': 'event', 'es': 'eventos'},
         'plugins.event.urls'),
    )

And your URL_DEFAULT_LANG is "es", the /eventos URL prefix will be used.

CACHE_BACKEND

Default: johnny.backends.locmem:///

CACHE_BACKEND is not a Merengue settings but a Django one, but we mention that settings because Merengue uses Johnny Cache as smart caching manager.

This implies you have to prepend johnny.backends. to your project caching backends in order to get it works with johnny-cache (see Johnny Cache backends). Example:

CACHE_BACKEND = 'johnny.backends.memcached://127.0.0.1:11211/'

CACHE_SITE_FOR_ANONYMOUS

Default: False

CACHE_SITE_FOR_ANONYMOUS activates the site template caching for anonymous requests. See Optimizing a Merengue installation.

TINYMCE_EXTRA_MEDIA

Default: { 'js': [], 'css': [] }

Sometimes is useful for your site add extra CSS or Javascript files inside Merengue HTML editor (TinyMCE). This would be useful to add your public styles into HTML editor to be even more WYSIWYG.

You need include all media without MEDIA_URL prefix. This is an example:

TINYMCE_EXTRA_MEDIA = {
    'js': [],
    'css': ['themes/yourtheme/css/layout.css'],
}

PLUGINS_DIR

Default: plugins

This setting defines when Merengue will look the plugins.

REQUIRED_PLUGINS

Default: ('core', )

A list with plugins required for the correct behaviour of your project. Those plugins will be installed and activated when database is created and synced in your project.

DETECT_NEW_PLUGINS

Default: False

Detect automatically new plugins when manager access to plugins admin view.

If DETECT_NEW_PLUGINS is False, registration of new plugins is done executing register_new_plugins command.

DETECT_BROKEN_PLUGINS

Default: True

Detect automatically new plugins when manager access to plugins admin view.

If DETECT_BROKEN_PLUGINS is False, broken plugins detection is done executing mark_broken_plugins command.

USE_GIS

Default: False

Activate GIS in Merengue. This must be defined previously to database creation.

MAP_FILTRABLE_MODELS

Default: ('base.basecontent',)

All models included will be displayed in a filter included in map view, when GIS is activated.

COMPRESS

Default: not DEBUG

This setting activate/deactivate compression in Javascript and CSS files. When deployment is done is recommended to activate this variable.

Note

This variable will be activated by default if DEBUG is False.

APPS_TO_TEST

Default: ('action', 'base', 'block', 'registry', 'perms', 'portal', 'pluggable', 'section', 'theming', 'viewlet', 'workflow', )

This settings define the applications will be tested when the testmerengue command is executed.

up