![]() ![]() In the Docker container, all files in the /app/data volume have to be Under the same user as Weblate itself is running, otherwise permissions on some You should also take care when running Management commands, as they should be ran When it does not have permissions to do so. Weblate tries to create these directories automatically, but it will fail You might prefer to move these to a better location such as: The default configuration places them in the same tree as the Weblate sources, however Owned and writable by the user running all Weblate processes (typically WSGI and Celery, see Running server and Background tasks using Celery). All files within this directory should be The Weblate process needs to be able to read and write to the directory where Gpg: Signature made Sun Mar 3 16:43:15 2019 CET gpg: using RSA key 87E673AF83F6C3A0C344C8C3F4AA229D4D58C245 gpg: BAD signature from "Michal Čihař " Filesystem permissions Once the key is trusted, the warning will not occur: You can trust the key transitively through signatures of others, who have met The most reliable method is to meet the developer in person andĮxchange key fingerprints, however you can also rely on the web of trust. Handbook covers this topic in the chapter Validating other keys on your public You need toĮnsure that the key is actually owned by the mentioned person. The problem here is that anybody could issue the key with this name. Gpg: assuming signed data in 'Weblate-3.5.tar.xz' gpg: Signature made Ne 3. března 2019, 16:43:15 CET gpg: using RSA key 87E673AF83F6C3A0C344C8C3F4AA229D4D58C245 gpg: Good signature from "Michal Čihař " gpg: aka "Michal Čihař " gpg: aka "" gpg: aka "Michal Čihař (Braiins) " gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Wheels while installing using pip or when you use distribution packages. ![]() This depends on how you install them, so please consult To build some of the Python dependencies you might need to install theirĭependencies. licensee (optional for detecting license when creating component) tesseract and its data (optional for screenshots OCR) git-svn (optional for Subversion support) ,, see Pango and Cairo git-review (optional for Gerrit support) Pango, Cairo and related header files and GObject introspection data The following dependencies have to be installed on the system: Git Weblate supports PostgreSQL, MySQL and MariaDB, see Database setup for Weblate andīackends documentation for more details. fluent.syntax (optional for Fluent format) Zeep (optional for Microsoft Terminology) python-akismet (optional for Spam protection) tesserocr (optional for OCR in Visual context for strings) Mercurial (optional for Mercurial repositories support) You can install dependencies using pip or from yourĭistribution packages, full list is available in requirements.txt.įollowing modules are necessary for some Weblate features. Weblate is written in Python and supports Pythonģ.6 or newer. SMTP server for outgoing e-mail, see Configuring outgoing e-mail. Redis server for cache and tasks queue, see Background tasks using Celery. PostgreSQL database server, see Database setup for Weblate. Weblate is using other services for its operation. Weblate is known to work on Linux, FreeBSD and macOS. ![]() ![]() Software requirements Operating system Installing from sources, recommended for development. Weblate testsuite and continuous integration.Translating HTML and JavaScript using Weblate CDN.Executing Celery tasks in the wsgi using eager mode.Sample configuration for Apache and Gunicorn.Sample configuration for NGINX and uWSGI.Configuring Weblate to use MySQL/MariaDB.Installing on RedHat, Fedora and CentOS. ![]()
0 Comments
Leave a Reply. |