NOT USE THIS SERVER IN A PRODUCTION SETTING. It has not gone through security audits or performance tests. See also Django documentation on runserver [https://docs.djangoproject.com/en/stable/ref/django- information to use natively Django inside PyCharm: the idea is to be able to immediately trigger the unit tests in the IDE. For that you need to specify the root path of Django and the path of one setting: Be [https://codecov.io/github/WeblateOrg/weblate]. There are several jobs to verify different aspects: Unit tests Documentation build and external links Migration testing from all supported releases Code linting

NOT USE THIS SERVER IN A PRODUCTION SETTING. It has not gone through security audits or performance tests. See also Django documentation on runserver. Hint: The Django built in server serves static files information to use natively Django inside PyCharm: the idea is to be able to immediately trigger the unit tests in the IDE. For that you need to specify the root path of Django and the path of one setting: 3.2 and coverage is reported on Codecov. There are several jobs to verify different aspects: • Unit tests • Documentation build and external links • Migration testing from all supported releases • Code

NOT USE THIS SERVER IN A PRODUCTION SETTING. It has not gone through security audits or performance tests. See also Django documentation on runserver. Hint: The Django built in server serves static files information to use natively Django inside PyCharm: the idea is to be able to immediately trigger the unit tests in the IDE. For that you need to specify the root path of Django and the path of one setting: 3.2 and coverage is reported on Codecov. There are several jobs to verify different aspects: • Unit tests • Documentation build and external links • Migration testing from all supported releases • Code

NOT USE THIS SERVER IN A PRODUCTION SETTING. It has not gone through security audits or performance tests. See also Django documentation on runserver. Hint: The Django built in server serves static files information to use natively Django inside PyCharm: the idea is to be able to immediately trigger the unit tests in the IDE. For that you need to specify the root path of Django and the path of one setting: 3.2 and coverage is reported on Codecov. There are several jobs to verify different aspects: • Unit tests • Documentation build and external links • Migration testing from all supported releases • Code

NOT USE THIS SERVER IN A PRODUCTION SETTING. It has not gone through security audits or performance tests. See also Django documentation on runserver [https://docs.djangoproject.com/en/stable/ref/django- information to use natively Django inside PyCharm: the idea is to be able to immediately trigger the unit tests in the IDE. For that you need to specify the root path of Django and the path of one setting: Be [https://codecov.io/github/WeblateOrg/weblate]. There are several jobs to verify different aspects: Unit tests Documentation build and external links Migration testing from all supported releases Code linting

NOT USE THIS SERVER IN A PRODUCTION SETTING. It has not gone through security audits or performance tests. See also Django documentation on runserver [https://docs.djangoproject.com/en/stable/ref/django- information to use natively Django inside PyCharm: the idea is to be able to immediately trigger the unit tests in the IDE. For that you need to specify the root path of Django and the path of one setting: Be [https://codecov.io/github/WeblateOrg/weblate]. There are several jobs to verify different aspects: Unit tests Documentation build and external links Migration testing from all supported releases Code linting

NOT USE THIS SERVER IN A PRODUCTION SETTING. It has not gone through security audits or performance tests. See also Django documentation on runserver. Hint: The Django built-in server serves static files script also accepts some parameters, to execute tests, run it with the test parameter and then specify any test parameters, for example running only tests in the weblate.machine module: ./rundev.sh test weblate.machine Note: Be careful that your Docker containers are up and running before running the tests. You can check that by running the docker ps command. To display the logs: ./rundev.sh logs To

NOT USE THIS SERVER IN A PRODUCTION SETTING. It has not gone through security audits or performance tests. See also Django documentation on runserver. Hint: The Django built-in server serves static files script also accepts some parameters, to execute tests, run it with the test parameter and then specify any test parameters, for example running only tests in the weblate.machine module: ./rundev.sh test weblate.machine Note: Be careful that your Docker containers are up and running before running the tests. You can check that by running the docker ps command. To display the logs: ./rundev.sh logs To

NOT USE THIS SERVER IN A PRODUCTION SETTING. It has not gone through security audits or performance tests. See also Django documentation on runserver. Hint: The Django built-in server serves static files script also accepts some parameters, to execute tests, run it with the test parameter and then specify any test parameters, for example running only tests in the weblate.machine module: ./rundev.sh test weblate.machine Note: Be careful that your Docker containers are up and running before running the tests. You can check that by running the docker ps command. To display the logs: ./rundev.sh logs To

NOT USE THIS SERVER IN A PRODUCTION SETTING. It has not gone through security audits or performance tests. See also Django documentation on runserver. Hint: The Django built-in server serves static files script also accepts some parameters, to execute tests, run it with the test parameter and then specify any test parameters, for example running only tests in the weblate.machine module: ./rundev.sh test weblate.machine Note: Be careful that your Docker containers are up and running before running the tests. You can check that by running the docker ps command. To display the logs: ./rundev.sh logs To