example.com record to match your real domain name. Once you are done, you should also check the Performance report in the admin interface, which will give you hints of potential non optimal configuration com/en/stable/ref/templates/api/#django.template.loaders.cached.Loader] Running maintenance tasks For optimal performance, it is good idea to run some maintenance tasks in the background. This is now automatically done in Django: ./manage.py runserver Warning Do not use this in production, as this has severe performance limitations. Serving static files Changed in version 2.4: Prior to version 2.4, Weblate didn’t

the example.com record to match your real domain name. Once you are done, you should also check Performance report in the admin interface which will give you hints for non optimal configuration on your site com/en/stable/ref/templates/api/#django.template.loaders.cached.Loader] Running maintenance tasks For optimal performance, it is good idea to run some maintenance tasks in the background. Changed in version 3.2: Since web server: ./manage.py runserver Warning Do not use this in production as this has severe performance limitations. Serving static files Changed in version 2.4: Prior to version 2.4 Weblate didn’t

the example.com record to match your real domain name. Once you are done, you should also check Performance report in the admin interface which will give you hints for non optimal configuration on your site com/en/stable/ref/templates/api/#django.template.loaders.cached.Loader] Running maintenance tasks For optimal performance, it is good idea to run some maintenance tasks in the background. Changed in version 3.2: Since web server: ./manage.py runserver Warning Do not use this in production as this has severe performance limitations. Serving static files Changed in version 2.4: Prior to version 2.4 Weblate didn’t

the example.com record to match your real domain name. Once you are done, you should also check Performance report in the admin interface which will give you hints for non optimal configuration on your site com/en/stable/ref/templates/api/#django.template.loaders.cached.Loader] Running maintenance tasks For optimal performance, it is good idea to run some maintenance tasks in the background. Changed in version 3.2: Since web server: ./manage.py runserver Warning Do not use this in production as this has severe performance limitations. Serving static files Changed in version 2.4: Prior to version 2.4 Weblate didn’t

the example.com record to match your real domain name. Once you are done, you should also check Performance report in the admin interface which will give you hints for non optimal configuration on your site com/en/stable/ref/templates/api/#django.template.loaders.cached.Loader] Running maintenance tasks For optimal performance, it is good idea to run some maintenance tasks in the background. Changed in version 3.2: Since web server: ./manage.py runserver Warning Do not use this in production as this has severe performance limitations. Serving static files Changed in version 2.4: Prior to version 2.4 Weblate didn’t

checks which you can see in the admin interface, just follow the Performance report link in the admin interface or open the /admin/performance/ URL directly. Why do links contain example.com as the domain can automatically detect several widely spread file formats, but this detection can harm your performance and will limit features specific to given file format (for example automatic adding of new translations) example.com record to match your real domain name. Once you are done, you should also check the Performance report in the admin interface, which will give you hints of potential non optimal configuration

checks which you can see in the admin interface, just follow the Performance report link in the admin interface or open the /admin/performance/ URL directly. Why do links contain example.com as the domain can automatically detect several widely spread file formats, but this detection can harm your performance and will limit features specific to given file format (for example automatic adding of new translations) example.com record to match your real domain name. Once you are done, you should also check the Performance report in the admin interface, which will give you hints of potential non optimal configuration

checks which you can see in the admin interface, just follow the Performance report link in the admin interface or open the /admin/performance/ URL directly. Why do links contain example.com as the domain can automatically detect several widely spread file formats, but this detection can harm your performance and will limit features specific to given file format (for example automatic adding of new translations) example.com record to match your real domain name. Once you are done, you should also check the Performance report in the admin interface, which will give you hints of potential non optimal configuration

checks which you can see in the admin interface, just follow the Performance report link in the admin interface or open the /admin/performance/ URL directly. Why do links contain example.com as the domain can automatically detect several widely spread file formats, but this detection can harm your performance and will limit features specific to given file format (for example automatic adding of new translations) example.com record to match your real domain name. Once you are done, you should also check the Performance report in the admin interface, which will give you hints of potential non optimal configuration

example.com record to match your real domain name. Once you are done, you should also check the Performance report in the admin interface, which will give you hints of potential non optimal configuration com/en/stable/ref/templates/api/#django.template.loaders.cached.Loader] Running maintenance tasks For optimal performance, it is good idea to run some maintenance tasks in the background. This is now automatically done in Django: ./manage.py runserver Warning Do not use this in production, as this has severe performance limitations. Serving static files Changed in version 2.4: Prior to version 2.4, Weblate didn’t