and WHOOSH_INDEX is used for fulltext search data. The default configuration places them in same tree as Weblate sources, however you might prefer to move these to better location such as /var/lib/weblate guide » Translation projects Translation organization Weblate organizes translatable content into tree like structure. The toplevel object is Project, which should hold all translations which belong together helpers for Bazaar and Mercurial (hg) are available within Git source code [https://github.com/git/git/tree/master/contrib/remote-helpers], they might be also included in your Git package. If this is not the

and WHOOSH_INDEX is used for fulltext search data. The default configuration places them in same tree as Weblate sources, however you might prefer to move these to better location such as /var/lib/weblate guide » Translation projects Translation organization Weblate organizes translatable content into tree like structure. The toplevel object is Project, which should hold all translations which belong together helpers for Bazaar and Mercurial (hg) are available within Git source code [https://github.com/git/git/tree/master/contrib/remote-helpers], they might be also included in your Git package. If this is not the

and WHOOSH_INDEX is used for fulltext search data. The default configuration places them in same tree as Weblate sources, however you might prefer to move these to better location such as /var/lib/weblate directory used by Weblate in settings.py, for example to set it to configuration directory under Weblate tree: os.environ['HOME'] = os.path.join(BASE_DIR, 'configuration') Note On Linux and other UNIX like control Translation projects Translation organization Weblate organizes translatable content into tree like structure. The toplevel object is Project, which should hold all translations which belong together

write to the directory where it keeps data - DATA_DIR. The default configuration places them in same tree as Weblate sources, however you might prefer to move these to better location such as /var/lib/weblate directory used by Weblate in settings.py, for example to set it to configuration directory under Weblate tree: os.environ['HOME'] = os.path.join(BASE_DIR, 'configuration') Note On Linux and other UNIX like control Translation projects Translation organization Weblate organizes translatable content into tree like structure. The toplevel object is Project configuration, which should hold all translations which

write to the directory where it keeps data - DATA_DIR. The default configuration places them in same tree as Weblate sources, however you might prefer to move these to better location such as /var/lib/weblate directory used by Weblate in settings.py, for example to set it to configuration directory under Weblate tree: os.environ['HOME'] = os.path.join(BASE_DIR, 'configuration') Note On Linux and other UNIX like control Translation projects Translation organization Weblate organizes translatable content into tree like structure. The toplevel object is Project configuration, which should hold all translations which

write to the directory where it keeps data - DATA_DIR. The default configuration places them in same tree as Weblate sources, however you might prefer to move these to better location such as /var/lib/weblate directory used by Weblate in settings.py, for example to set it to configuration directory under Weblate tree: os.environ['HOME'] = os.path.join(BASE_DIR, 'configuration') Note On Linux and other UNIX like control Translation projects Translation organization Weblate organizes translatable content into tree like structure. The toplevel object is Project configuration, which should hold all translations which

write to the directory where it keeps data - DATA_DIR. The default configuration places them in same tree as Weblate sources, however you might prefer to move these to better location such as /var/lib/weblate directory used by Weblate in settings.py, for example to set it to configuration directory under Weblate tree: os.environ['HOME'] = os.path.join(BASE_DIR, 'configuration') Note: On Linux and other UNIX like Translation projects 4.5.1 Translation organization Weblate organizes translatable content into tree like structure. The toplevel object is Project configuration, which should hold all translations which

write to the directory where it keeps data - DATA_DIR. The default configuration places them in same tree as Weblate sources, however you might prefer to move these to better location such as /var/lib/weblate directory used by Weblate in settings.py, for example to set it to configuration directory under Weblate tree: os.environ['HOME'] = os.path.join(BASE_DIR, 'configuration') Note: On Linux and other UNIX like Translation projects 4.7.1 Translation organization Weblate organizes translatable content into tree like structure. The toplevel object is Project configuration, which should hold all translations which

write to the directory where it keeps data - DATA_DIR. The default configuration places them in same tree as Weblate sources, however you might prefer to move these to better location such as /var/lib/weblate directory used by Weblate in settings.py, for example to set it to configuration directory under Weblate tree: os.environ['HOME'] = os.path.join(BASE_DIR, 'configuration') Note On Linux and other UNIX like control Translation projects Translation organization Weblate organizes translatable content into tree like structure. The toplevel object is Project configuration, which should hold all translations which

and WHOOSH_INDEX is used for fulltext search data. The default configuration places them in same tree as Weblate sources, however you might prefer to move these to better location such as /var/lib/weblate Translation projects 4.5.1 Translation organization Weblate organizes translatable content into tree like structure. The toplevel object is Project, which should hold all translations which belong together Weblate Documentation, Release 1.8 5.4.3 Why does Weblate force to have show all po files in single tree? Weblate was designed in a way that every po file is represented as single subproject. This is beneficial