The most basic way to set up a remote repository is to simply point an anonymous

The most basic way to set up a remote repository is to simply point an anonymous

-

FTP server to any working SWORD module installation (i.e. if

+

[http://en.wikipedia.org/wiki/File_Transfer_Protocol FTP] server to any working SWORD module installation (i.e. if

'''/usr/share/sword''' works for your front-ends, then expose this directory

'''/usr/share/sword''' works for your front-ends, then expose this directory

via your FTP server and your module repository is done).

via your FTP server and your module repository is done).

Line 9:

Line 9:

== Complete layout of a larger module repository ==

== Complete layout of a larger module repository ==

-

In order to deal with all ways the various front-ends use our module [http://en.wikipedia.org/wiki/Repository repository] the following should be provided:

+

To optimize a repository with a larger number of modules, an archive file of the mods.d directory should be created. The repository will work fine without this but adding the file will speed up use of the repository for remote users.

-

+

-

An echo of the '''mods.d''' and '''modules''' area as found under any Sword module area on your system (e.g. '''~/.sword''') a directory with zipped modules for JSword derived front-ends. This can also serve as a repository for smaller devices without integrated module manager.

+

-

+

-

This needs to be accessible either via FTP or via HTTP, preferentially by both. FTP is more reliable for a variety of reasons.

+

-

+

-

To optimize a repository with a larger number of modules, the '''mods.d.tar.g'''

+

-

archive file of the mods.d directory can be created. The repository

+

-

will work fine without this but adding the file will speed up use of the repository for remote users.

+

tar czvf mods.d.tar.gz mods.d/*

tar czvf mods.d.tar.gz mods.d/*

-

== Zipped Modules ==

+

JSword front-ends require at the moment (though not for much longer) the presence of the modules as [[Zipped modules| zipped archive files]]. Having these available will also likely be a way in the future to make interaction with remote users faster.

-

+

-

Some of the smaller devices running a sword front-end do not have a network enabled module manager. Users of these devices need to download their modules as zipped files and unzip them in the right place - e.g. a SD card.

+

-

+

-

It is also helpful for people who have no access to direct internet connections or live in countries with monitored access to the internet[1] to be able to download (and possibly distribute) zipped modules. This is a zipped archive of a module in the file and directory layout used in the local module directory.

+

-

+

-

E.g. to create from your own module directory a zipped module of a uncompressed GenBook do this:

Most front-ends can install modules from a number of repositories. All recognised repositories are listed in [[Module Repositories]]. These repositories are well established with CrossWire and are maintained by various developers. If you or your organisation have set up your own repository, please announce it on the mailing list (sword-devel@crosswire.org).

Most front-ends can install modules from a number of repositories. All recognised repositories are listed in [[Module Repositories]]. These repositories are well established with CrossWire and are maintained by various developers. If you or your organisation have set up your own repository, please announce it on the mailing list (sword-devel@crosswire.org).

-

From libsword-1.5.12 onwards the module manager will also be able to load dynamically a list of active and accepted repositories. To enable your repository for this list please contact CrossWire. We will then decide whether we will list your repository as endorsed by us.

+

The module manager is able to load dynamically a list of active and accepted repositories. To enable your repository for this list please contact CrossWire. We will then decide whether we will list your repository as endorsed by us. We would not endorse a repository that has content in breach of [[copyright]].

Latest revision as of 15:22, 14 June 2012

Contents

A simple repository

The most basic way to set up a remote repository is to simply point an anonymous
FTP server to any working SWORD module installation (i.e. if
/usr/share/sword works for your front-ends, then expose this directory
via your FTP server and your module repository is done).

All our frontends should be able then to access this repository and download your modules.

Complete layout of a larger module repository

To optimize a repository with a larger number of modules, an archive file of the mods.d directory should be created. The repository will work fine without this but adding the file will speed up use of the repository for remote users.

tar czvf mods.d.tar.gz mods.d/*

JSword front-ends require at the moment (though not for much longer) the presence of the modules as zipped archive files. Having these available will also likely be a way in the future to make interaction with remote users faster.

Registering your repository with CrossWire

Most front-ends can install modules from a number of repositories. All recognised repositories are listed in Module Repositories. These repositories are well established with CrossWire and are maintained by various developers. If you or your organisation have set up your own repository, please announce it on the mailing list (sword-devel@crosswire.org).

The module manager is able to load dynamically a list of active and accepted repositories. To enable your repository for this list please contact CrossWire. We will then decide whether we will list your repository as endorsed by us. We would not endorse a repository that has content in breach of copyright.