ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #weblate
Discover how Weblate separates UI and heavy file parsing with Celery, Redis, and PostgreSQL, and learn operational checks to keep the translation pipeline healthy.
Learn how to enable Weblate's shared translation memory to reuse approved strings across components, cut translation effort, and avoid common pitfalls.
Learn how to eliminate translation drift by configuring Weblate's Git synchronization. This guide covers repository connection, push/pull triggers, and conflict resolution.
How Weblate's Automatic translation add-on works, a safe bootstrap configuration that never overwrites human translations, and the limits teams hit with machine translation at scale.
Goal is to keep editor save latency predictable when multiple users edit the same project via Weblate UI or API. Weblate stores translation units with Django ORM transactions. Background work for commits, translation memory indexing and machine translation suggestions runs via Celery on the same database. With default queues, UI requests can contend for I/O
Synchronization Boundary Analysis Weblate manages translation data by mirroring a database state with a remote Git repository. This integration relies on asynchronous Celery tasks to handle pushes and pulls, ensuring that UI responsiveness is maintained during large commit operations. A critical design constraint involves the interaction between Weblate's au
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
django
git