Главная   Изменения   Спек   Патчи   Исходники   Загрузить   Gear   Bugs and FR  Repocop 

The Fedora Extras build of monotone provides an extra RPM monotone-server.
This package is intended to make it easy to set up an unattended server
installation for Monotone's Netsync protocol (i.e. "monotone serve").

The package a standard Fedora-style init.d script with chkconfig support
for running the server, installed as /usr/sbin/monotone-server.
(This is just a symlink to monotone that the init script runs instead.
This enables matching "monotone-server" processes with ps to distinguish
server instances from people using monotone.)

The /etc/monotone directory serves as ~/.monotone for the server.  This
directory and its contents are not writable by the "monotone" user ID under
which the network server runs.  The database lives in /var/db/monotone,
which the "monotone" user ID must write to.

The init.d script will generate a private key for the server to use, if
none exists yet.  The key identification will be the host's FQDN (from
/bin/hostname -f).  You can use "service monotone genkey [IDENT]" to
generate the private key by hand and set up the unattended server to use
it, supplying a different key identification string if you like.

Before starting the server, the script will migrate an old database
format if you had a previous version of the monotone-server installation.
(This includes converting private keys from the old format.)
You can always do this explicitly with "service monotone migrate".

Access to the server is controlled by the /etc/monotone/read-permissions and
/etc/monotone/write-permissions files, unless you write your own Lua hooks
in /etc/monotone/monotonerc.  These files are not created or editted by the
RPM scripts, you must create them.  These files refer to key identification
strings for keys already the database.  Anyone allowed write access by the
netwrok server can put new keys in the database with "monotone push" using
the --key-to-push option.  To bootstrap this, /etc/monotone/write-permission
must allow some key and that key must be in the database already.  You can
put a key in the server's database easily with "service monotone import",
e.g. to import the public key for a private key in ~/.monotone/keys:

	mtn pubkey me@my.com | sudo service monotone import

For problems with this package or its scripts, please file bugs
at http://bugzilla.redhat.com/ for the "monotone" component
in th "Fedora Extras" product.