I have a bunch of basic questions about FSVS that aren't really
addressed on the pages over at fsvs.tigris.org. Or maybe they're not
spelled out clearly.
1) Is the backend repository for FSVS a standard Subversion repository?
Is FSVS simply another client-side tool for talking to a SVN
repository (but with some additional power)?
2) Assuming #1 is true, we can lock things down a bit using the
"command=" feature associated with the SSH public key used to connect to
the SVN repository server? For example, we configure our
~/.ssh/authorized_keys file as:
command="/usr/bin/svnserve -t -r /var/svn",no-agent-forwarding,no-pty
ssh-rsa (ssh-key) (comment)
Which limits the user to running only the svnserve daemon. We also have
the following defined in /etc/ssh/sshd_config:
AllowTcpForwarding no
X11Forwarding no
PermitTunnel no
In addition, the user account on the SVN server can only access their
repository folder under /var/svn.
3) What are the advantages to using separate repositories for each
machine vs putting them all in a single repository? It seems like it
would be better to use separate repositories (along with individual SSH
keys for each client machine).
The FSVS site shows a large tree with base/, user/, machine/, software/
and I'm wondering how well that works out in practice.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
