Child pages
  • Connect to version control system
Skip to end of metadata
Go to start of metadata

How to connect oTranCe to a version control system

oTranCe stores the exported files into the folder data/export/.

To put this folder under version control you need to checkout your repository to this folder. E.g.:

svn checkout http://yourRepository/trunk/yourLanguageFolder/ data/export/

Now your export folder is taken under version control. Each time you hit the "Export" button in oTranCe, the VCS will take care of changes. When you - or one of your oTranCe users having the right - hit the "Export to VCS" button in the GUI of oTranCe, it will trigger the svn commit command and changes will be pushed to your repository.

Take care that the relative paths you use in the file templates map the entry point of your repository. If the language files in your repository are placed at

yourRepository/trunk/core/language/ and in the file templates of oTranCe you defined the starting point relative to the language folder (e.g. {LOCALE}/lang.php) you want to reflect that by checking out the repository at the level of the language folder:

svn checkout http://yourRepository/trunk/core/language/ data/export/


Commiting via oTranCe

In order to be able to commit to the repository oTranCe needs to use a VCS user that has commit rights. In the admin panel you can provide the necessary information.

You can add options that are specific to your vcs version and setup. 

The provided general VCS user will be used for commits if the current oTranCe user doesn't have configured an own VCS user.

If VCS is activated any oTranCe user is able to configure his own VCS user in his personal settings:

If this oTranCe user is allowed to use the "Export to VCS" button and he has configured his own VCS user, it will be used for the commit.


  • No labels