#localeapp.com

Localisation (i18n)

All  app translations are stored in <locale>.yml files, and synced to localeapp.com. Only those files are synced. Examples: en.yml nb.yml

System translations (for rails, rails_admin, or language defaults like date and time localisations) should be stored in their own .yml files and thus NOT synced to localeapp.com. This will keep your translation key count down.

Heroku will sync (pull) automatically from localeapp.com every 60 seconds, or on page refresh. If do this implementation: this: https://github.com/Locale/localeapp/wiki/Deploy-a-Locale-Backed-Application-to-Heroku

The daemon is mainly made for for privately managed servers, where you want to pull translations regularly. But it can also be used on localhost. To pull all up-to-date translations, run (works only as a pull): `localeapp daemon`

The localhost app will sync on page refresh, for that specific page. So the daemon is not strictly needed, unless you have someone besides yourself constantly updating translations on localeapp.com. Pushing local changes to localeapp.com: If you change the en.yml/nb.yml files locally you must remember to run: `localeapp push config/locales/<locale>.yml` for the respective locale files you updated (replace <locale> with either en or nb or similar). 

That is the only way localeapp.com will get your local changes to those files.

After pushing, check for potential errors here: `http://www.localeapp.com/projects/<localeapp_project_id>/imports` (localeapp_project_id is the project ID on localeapp.com, you can see it from the URL when you're logged in there and viewing the translations for your project.) since the localeapp push won't show errors in the terminal directly.