Pin ask staging branch to 0.7.x and update settings

The askbot branches were separated by major versions, in the upstream
repository so this patch pins the ask-staging to the 0.7.x.
The 0.7.x. branch works with django version 1.5.x.

Settings.py now contains the new language configuration options,
including the ASKBOT_LANGUAGE_MODE settings and the required
captcha module.

Change-Id: Icd1052da20396601010315447a385fe7353391cd
This commit is contained in:
Marton Kiss 2016-01-11 16:17:59 +01:00
parent e777d234a7
commit f4026f4859
2 changed files with 7 additions and 1 deletions

View File

@ -92,6 +92,7 @@ class openstack_project::ask_staging (
# askbot site
class { 'askbot':
askbot_branch => '0.7.x',
db_provider => 'pgsql',
db_name => $db_name,
db_user => $db_user,

View File

@ -97,6 +97,7 @@ SECRET_KEY = '44fb9b7219e3743bffabb6861cbc9a28'
# List of callables that know how to import templates from various sources.
TEMPLATE_LOADERS = (
'askbot.skins.loaders.Loader',
'askbot.skins.loaders.JinjaAppDirectoryLoader',
'django.template.loaders.app_directories.Loader',
'django.template.loaders.filesystem.Loader',
#'django.template.loaders.eggs.load_template_source',
@ -198,10 +199,13 @@ INSTALLED_APPS = (
'followit',
'tinymce',
'group_messaging',
'captcha',
#'avatar',#experimental use git clone git://github.com/ericflo/django-avatar.git$
)
NOCAPTCHA = True
#setup memcached for production use!
#see http://docs.djangoproject.com/en/1.1/topics/cache/ for details
CACHE_BACKEND = 'locmem://'
@ -398,7 +402,7 @@ GROUP_MESSAGING = {
'BASE_URL_PARAMS': {'section': 'messages', 'sort': 'inbox'}
}
ASKBOT_MULTILINGUAL = True
ASKBOT_LANGUAGE_MODE = 'url-lang'
LANGUAGES = (
('en', 'English'),
@ -418,6 +422,7 @@ if 'ASKBOT_CSS_DEVEL' in locals() and ASKBOT_CSS_DEVEL == True:
COMPRESS_JS_FILTERS = []
COMPRESS_PARSER = 'compressor.parser.HtmlParser'
JINJA2_EXTENSIONS = ('compressor.contrib.jinja2ext.CompressorExtension',)
JINJA2_TEMPLATES = ('captcha',)
# Use syncdb for tests instead of South migrations. Without this, some tests
# fail spuriously in MySQL.