'Simultaneous use of yaml and database to store translations
I'm currently using i18n. I'm thinking about using both YAML and DB for translations because required workflow is next: developer creates default translation in yaml file and some admin users change them. I see next solution: somehow merge both translation with priority to DB version. The problem is how to do this?
Solution 1:[1]
One of the workarounds can be importing / merging one into another. Turn on file-based translations by default in development environment and db-based in production and import translation files into database on deployment script (capistrano, etc).
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|---|
| Solution 1 | dmskr |