##// END OF EJS Templates
caches: use individual namespaces per user to prevent beaker caching problems....
caches: use individual namespaces per user to prevent beaker caching problems. - especially for mysql in case large number of data in caches there could be critical errors storing cache, and thus preventing users from authentication. This is caused by the fact that we used single namespace for ALL users. It means it grew as number of users grew reaching mysql single column limit. This changes the behaviour and now we use namespace per-user it means that each user-id will have it's own cache namespace fragmenting maximum column data to a single user cache. Which we should never reach.

File last commit:

r1098:5d0049e7 default
r2591:36829a17 stable
Show More
setup.cfg
43 lines | 789 B | text/x-ini | IniLexer
[aliases]
test = pytest
[egg_info]
tag_build =
tag_svn_revision = false
# Babel configuration
[compile_catalog]
domain = rhodecode
directory = rhodecode/i18n
statistics = true
[extract_messages]
add_comments = TRANSLATORS:
output_file = rhodecode/i18n/rhodecode.pot
msgid-bugs-address = marcin@rhodecode.com
copyright-holder = RhodeCode GmbH
no-wrap = true
keywords =
lazy_ugettext
_ngettext
_gettext
gettext_translator
[init_catalog]
domain = rhodecode
input_file = rhodecode/i18n/rhodecode.pot
output_dir = rhodecode/i18n
[update_catalog]
domain = rhodecode
input_file = rhodecode/i18n/rhodecode.pot
output_dir = rhodecode/i18n
previous = true
[build_sphinx]
source-dir = docs/
build-dir = docs/_build
all_files = 1
[upload_sphinx]
upload-dir = docs/_build/html