Creating and Maintaining a Module Repository - Revision history

Refdoc: /* Registering your repository with CrossWire */

2018-01-10T15:35:18Z

‎Registering your repository with CrossWire

2018-01-08T13:58:02Z

2012-06-14T15:22:53Z

2012-01-17T17:26:36Z

‎A simple repository: [http://en.wikipedia.org/wiki/File_Transfer_Protocol FTP]

2011-02-01T10:00:10Z

‎Registering your repository with CrossWire: copyright

2011-02-01T09:59:26Z

‎Registering your repository with CrossWire: We would not endorse a repository that has content in breach of copyright.

2010-11-05T17:48:49Z

‎Complete layout of a larger module repository

2010-11-05T17:42:09Z

‎see also: See

2010-11-05T17:41:42Z

‎Complete layout of a larger module repository: the

2010-11-05T17:40:29Z

‎Complete layout of a larger module repository: front-ends

@@ Line 17: / Line 17: @@
 == 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).
+Most front-ends can install modules from a number of repositories. All recognised repositories are listed in [[Official and Affiliated 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]].

← Older revision		Revision as of 13:58, 8 January 2018
Line 23:		Line 23:
	== See also ==		== See also ==

−	[[Zipped modules]]	+	* [[Zipped modules]]
		+	* [[Modules_in_the_beta_repository\|Testing status of Beta modules]]

← Older revision		Revision as of 15:22, 14 June 2012
Line 28:		Line 28:
	[[Category:Guides\|Creating and Maintaining a Module Repository]]		[[Category:Guides\|Creating and Maintaining a Module Repository]]
	[[Category:Modules\|Creating and Maintaining a Module Repository]]		[[Category:Modules\|Creating and Maintaining a Module Repository]]
		+	[[Category:Repositories\|Creating and Maintaining a Module Repository]]

@@ Line 1: / Line 1: @@
 ==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
+[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
 via your FTP server and your module repository is done).

@@ Line 19: / Line 19: @@
 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.
+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]].
 == See also ==

@@ Line 13: / Line 13: @@
   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 modules| zipped archive files]]. Having these available will also likely be a way in the future to make interaction with users faster.
+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.
 == Registering your repository with CrossWire ==

@@ Line 21: / Line 21: @@
 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.
-== see also ==
+== See also ==
 [[Zipped modules]]