manThe Grimoire Python action-tree implemen - Cookbook: recipe #101, Setting up a tla archive

Show feedback again

recipe #101, Source Code Managers: Setting up a tla archive

(First, you should make sure that your SSH access is set up. If you are not sure, read recipe #102)

There is currently more than one way to work with GNU arch: the decentralized way and the centralized way.

Setting up a public archive mirror (decentralized way):

The most common way of using arch is the decentralized way: the developer works with his local archive and publishes it on a regular basis.

Let's assume
is your local archive, where 'project' is your project name.

Firstly, setup your public archive at with the following command ('archive-2004' is the symbolic name for your public archive location)

Then, synchronize your public archive:

Usually, it is more practical to synchronize your public archive whenever commits are done into the local archive. This can be achieved by the means of a commit hook. A hook is a small shell script that is run by tla when commands are run. It is located at ~/.arch-params/hook.

Here is an example:

(Please note that your public mirror is locally know as local-archive-name-MIRROR)

Setting up a centralized public archive:

If you want several developers to commit direclty into the same public archive, you may be interested in making the public archive the main one, so every authorized commiter can access it at any time.

This can be done that way:

Accessing a tla project archive:

Firstly, register the tla archive with:

Then, retrieve the archive revision into a local directory:

For more details about GNU arch, please consider reading the documentation available at
A community wiki is also worth browsing at

Last update: Wed Mar 10 08:47:08 2010
This recipe comes from Gna! User Docs






Audience and Context

   All Project Members
   Source Code Manager: GNU Arch Repositories
Show feedback again

Back to the top

Powered by Savane 3.1-cleanup