Synchronizing data with the Git-annex Assistant
On the Server
A server accessible via the Internet extends the existing setup. To do this, you again need to install Git-annex on a particular machine and use the wizard in the browser to create a new repository.
In the dashboard, the Add another repository button provides an overview of possible locations. Select the Remote server entry from the list with the description Set up a repository on a remote server using ssh. SSH with public key authentication eliminates the problem of password entry during the configuration.
After filling out the dialogs, entering the hostname, username, and directory, the software creates the necessary files and starts syncing. A final menu (Figure 2) also points out that the SSH server uses a repository belonging to the transfer group.
Groups of this type keep the data long enough to allow it to be distributed to the clients. This approach avoids data ballast accumulating on the server. A transfer repository would thus even be possible on a server with limited storage space.
In addition to the transfer group, Git-annex defines nine other standard groups [4]. Depending on the application, you can assign a repository to one of these groups. The groups integrate predefined rules for distributing data. The program decides on the basis of these rules which data to keep and which to distribute to other repositories (see Table 1).
Table 1
Groups
Group | Content |
---|---|
client |
Keeps all data except the data in the archive directory. |
transfer |
Transfers data to other repositories; only keeps the files until all clients have a copy. |
backup |
Keeps all data in the repository. |
incremental backup |
Keeps all data that does not exist in another backup or another repository of the same type. |
small archive |
Prefers data in an archive directory and data not archived elsewhere. |
full archive |
Contains all data not archived elsewhere. |
source |
A repository that produces data, but does not contain any. Removes the data as soon as it is synchronized elsewhere. |
manual |
Allows manual definition of rules. |
public |
Suitable for publishing data. A configurable directory is synced with a public repository. |
unwanted |
For deleting and purging a repository. This assignment ensures that the software tranfers all data out. |
Remote Sharing
Assume members of the field staff want to access the existing repository on the server and synchronize data with the workgroup. They configure a local repository and the same remote server as their colleagues. In principle, the team can now exchange data via the central server, but for the time being, this is a manual process (Listing 4). For fully automated synchronization, further steps are necessary.
Listing 4
Using a Central Server
Automatic
The previously mentioned intermediate step for automatic synchronization relies on a tool that informs other clients about changes (Figure 3).
In the current version of Git-annex, this role is assumed by an XMPP or a Jabber server, which the clients use to set up remote pairing with their friends. Alternatively, messaging services such as Google Talk are suitable.
Joey Hess, the developer of Git-annex is working on a daemon that removes the intermediate step [5]. It monitors remote databases and automatically starts the sync when needed. The daemon has already made it into the main branch of development; a stable version is thus likely to appear in the not too distant future.
If you want to manage all of the components yourself, you can install your own messaging server, such as Ejabberd. However, the packages from Debian "Wheezy" and Ubuntu "Precise" do not work with Git-annex Assistant: A bug in the authentication mechanism prevents the configuration via the interface [6].
However, installer scripts exist for Ejabberd on the project website that facilitate the manual setup. On Ubuntu, you need the libyaml-0-2 package; then, just a few commands set up your own Jabber server that cooperates with Git-annex.
The Jabber server is the final component in remote sharing. The clients in the workgroup – including that used by a field employee – only need to accept one another as chat friends. In the web interface they use the Share with a friend menu item to enter the Jabber account name.
In the following screen, the names of active friends and a button labeled Start pairing appear. This button sends a pair request, which the communication partner needs to confirm. After this final step in the configuration, the clients synchronize their data via the transfer repository.
« Previous 1 2 3 Next »
Buy this article as PDF
(incl. VAT)
Buy Linux Magazine
Subscribe to our Linux Newsletters
Find Linux and Open Source Jobs
Subscribe to our ADMIN Newsletters
Support Our Work
Linux Magazine content is made possible with support from readers like you. Please consider contributing when you’ve found an article to be beneficial.
News
-
Canonical Bumps LTS Support to 12 years
If you're worried that your Ubuntu LTS release won't be supported long enough to last, Canonical has a surprise for you in the form of 12 years of security coverage.
-
Fedora 40 Beta Released Soon
With the official release of Fedora 40 coming in April, it's almost time to download the beta and see what's new.
-
New Pentesting Distribution to Compete with Kali Linux
SnoopGod is now available for your testing needs
-
Juno Computers Launches Another Linux Laptop
If you're looking for a powerhouse laptop that runs Ubuntu, the Juno Computers Neptune 17 v6 should be on your radar.
-
ZorinOS 17.1 Released, Includes Improved Windows App Support
If you need or desire to run Windows applications on Linux, there's one distribution intent on making that easier for you and its new release further improves that feature.
-
Linux Market Share Surpasses 4% for the First Time
Look out Windows and macOS, Linux is on the rise and has even topped ChromeOS to become the fourth most widely used OS around the globe.
-
KDE’s Plasma 6 Officially Available
KDE’s Plasma 6.0 "Megarelease" has happened, and it's brimming with new features, polish, and performance.
-
Latest Version of Tails Unleashed
Tails 6.0 is based on Debian 12 and includes GNOME 43.
-
KDE Announces New Slimbook V with Plenty of Power and KDE’s Plasma 6
If you're a fan of KDE Plasma, you'll be thrilled to hear they've announced a new Slimbook with an AMD CPU and the latest version of KDE Plasma desktop.
-
Monthly Sponsorship Includes Early Access to elementary OS 8
If you want to get a glimpse of what's in the pipeline for elementary OS 8, just set up a monthly sponsorship to help fund its continued existence.