ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #weblate
Weblate utilizes Celery and Redis to manage asynchronous translation tasks. During a version upgrade, the system executes Django migrations to update the PostgreSQL schema and updates the application logic to handle new task signatures. A critical boundary exists between the persistent database state and the volatile task queue in Redis. If an upgrade fails
Goal: Ensure that automated deployment scripts continue to create service accounts after upgrading to Weblate 4.16, where the default value of ENABLE_REGISTRATION changed from True to False . Uncertainty remains about whether the environment variable WEBLATE_ENABLE_REGISTRATION=1 is reliably honored in containerized installations and what exact HTTP response
Weblate's REST API pagination for component and translation listings uses Django REST Framework's limit/offset mechanism with a default page size of 50 items. This approach becomes problematic when automated tools need to iterate through large translation catalogs containing thousands of components. The DEFAULT_PAGE_SIZE configuration setting controls this d
Permission inheritance for machine-translated strings Weblate applies project-level permission boundaries to control whether contributors can commit translations directly or require coordinator review. When automatic translation suggestions are enabled via the integrated machine translation APIs, the system populates translation fields with suggestions that
Weblate's outbound HTTPS repository access relies on the host operating system's TLS stack and certificate trust store rather than a Weblate-specific CA configuration. When adding or updating a component from an external version-control host that presents an internally signed certificate, administrators may encounter TLS validation errors in the Weblate inte
When deploying Weblate in a private environment, the goal is to ensure the application is not unintentionally exposed to the public internet or open to anonymous user registration. Standard security practices involve using a reverse proxy for authentication and setting DEBUG=False . However, there is uncertainty regarding the most effective combination of in
Synchronization Concurrency in Weblate Weblate employs a push‑pull mechanism via a Celery-based task queue to synchronize translation units between the PostgreSQL database and version control systems. In environments with high‑frequency commits, the asynchronous nature of these tasks can lead to a backlog or potential race conditions when multiple updates ta
Permission Resolution in Multi-Group Scenarios Weblate implements role-based access control where users can inherit permissions from multiple groups across different authentication backends. The documentation indicates that users receive combined permissions from all their group memberships, but does not explicitly define how conflicts are resolved when grou
Determine how Weblate applies rate limits when both per‑user and per‑IP thresholds are configured. The built‑in API rate‑limiting feature uses the WEBLATE_RATE_LIMIT setting and returns standard headers, but the documentation does not state whether the two limits are evaluated independently or if the more restrictive limit is enforced. This ambiguity affects
redis