Pootle FS is Pootle’s integration with version control plugin systems. It allows Pootle to synchronize with an external repository containing your translations, keep them synchronised and manage and resolve any conflicts either automatically or via user input.
Warning
Pootle FS is considered beta in Pootle 2.8.0. We’d love you to try it out but please be aware that if you are basing production installs on Pootle FS that you can expect changes that might require manual intervention.
At any time we are able to query the state of Pootle FS using fs
state
command. The results of this operation will indicate if there
are any actions you need to specify to resolve any conflicts or if there are
untracked files.
You specify Actions that need to be taken to resolve conflicts or to ensure that files are tracked. This could be adding a file, removing a file or merging conflicting translations. This is the process of staging actions.
The final step is to synchronise Pootle and your filesystem. This operation takes your staged actions and executes them.
A filesystem is actually itself a Pootle FS plugin. Currently two exist:
You can write a plugin for any version control system, Pootle FS will ensure that the same commands and operations are used to ensure Pootle and your filesystem stay synchronized.
Note
Read this if you have used previous versions of Pootle.
Previous versions of Pootle made use of two commands, update_stores
and sync_stores
, to allow translations to be pushed into Pootle or
pulled from Pootle.
These two commands still exist but we will be phasing these out in the long term to make everything use Pootle FS.
You can find an outline of how to use Pootle FS on your existing Pootle projects in the adding a Pootle FS managed project instructions.
Once you are familiar with Pootle FS you can start migrating your projects to Pootle FS.