What specific file formats does Traduora support for importing and exporting translation keys?
Traduora supports common localization file formats such as JSON, YAML, PO, and others, allowing for flexible integration with various development stacks and existing translation resources.
Can Traduora be integrated directly into a CI/CD pipeline for automated translation updates?
Yes, Traduora offers a developer-friendly API that enables integration into CI/CD pipelines, allowing for automated fetching and pushing of translation keys and strings as part of your build and deployment processes.
How does Traduora handle version control for translation strings, and can I revert to previous translations?
Traduora includes built-in version control for all translation strings, allowing users to track changes over time and revert to previous versions if necessary, ensuring accuracy and providing an audit trail for all localization efforts.
What are the minimum technical requirements for self-hosting a Traduora instance?
While specific minimum requirements can vary based on usage, self-hosting Traduora typically requires a server environment capable of running Docker, along with a database (e.g., PostgreSQL) and sufficient memory and CPU resources to handle your team's translation volume.