You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Henrik Thostrup Jensen <ht...@cs.aau.dk> on 2005/04/09 22:41:02 UTC
Feature suggestion for read-only access to fsfs repos over http
Hi
I discussed this on #svn, and it was said that I would not like the answer
to this but I'm gonna try anyway :-).
I have a local fsfs repo, which I want to allow read-only access to one of
my friends. Unfortunately he does have access to the development machine
and I cannot run a server on the machine, since it is heavily firewalled.
The only way I have to export the data is over plain http (I have no need
for secrecy with the project). I tried symlinking to the repo within my
.public_html, but I got 301 error when trying to check it out. I read the
FAQ on the subject, and think I understand why I get it, but I cannot
change httpd.conf (nor do I really want to).
While I can do all sorts of hackish ways to solve the problem (post-commit
hook or cron job to produce directories/tarballs/emails) I would like to
able to do checkout over http and update directly from it. I don't see why
this should be much different than checking out from a local read-only
fsfs repo.
Please CC as I am not subscribed.
Best regards, Henrik
stud.scient Henrik Thostrup Jensen
Department of Computer Science, Aalborg University
E-mail: htj -at- cs.aau.dk, WWW: http://www.cs.aau.dk/~htj/
--
"My other car is a cdr."
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Feature suggestion for read-only access to fsfs repos over http
Posted by Ben Collins-Sussman <su...@collab.net>.
On Apr 10, 2005, at 8:15 AM, Marcus Rueckert wrote:
> On 2005-04-10 07:58:38 -0500, Ben Collins-Sussman wrote:
>>> I discussed this on #svn, and it was said that I would not like the
>>> answer to this but I'm gonna try anyway :-).
>>
>> At the moment, that thing is mod_dav_svn. What's the alternative?
>> What else could it possibly be? What's your proposal?
>>
>> Also, keep in mind that a client running 'svn checkout http://' is
>> issuing all sorts of WebDAV/DeltaV commands. It's not just doing a
>> series of GET requests, it's much more complex than that.
>>
>
> ben he wants a http backend for libsvn_repos. it should fetch the
> needed
> files via http and do its work with them.
>
I still don't understand... you mean a new back-end for libsvn_fs? We
have one backend which reads BDB, another which reads FSFS. So this a
suggestion for an fs back-end which speaks HTTP over a network? If so,
to what? Some sort of server, right? How does that server work?
Either way, it seems preposterous to me to write an fs back-end that
does networking. We *already* have an abstracted network layer, with
different server implementations.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Feature suggestion for read-only access to fsfs repos over http
Posted by Marcus Rueckert <da...@web.de>.
On 2005-04-10 07:58:38 -0500, Ben Collins-Sussman wrote:
> >I discussed this on #svn, and it was said that I would not like the
> >answer to this but I'm gonna try anyway :-).
>
> At the moment, that thing is mod_dav_svn. What's the alternative?
> What else could it possibly be? What's your proposal?
>
> Also, keep in mind that a client running 'svn checkout http://' is
> issuing all sorts of WebDAV/DeltaV commands. It's not just doing a
> series of GET requests, it's much more complex than that.
>
ben he wants a http backend for libsvn_repos. it should fetch the needed
files via http and do its work with them.
darix
--
irssi - the client of the smart and beautiful people
http://www.irssi.de/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Feature suggestion for read-only access to fsfs repos over http
Posted by Ben Collins-Sussman <su...@collab.net>.
On Apr 9, 2005, at 5:41 PM, Henrik Thostrup Jensen wrote:
> Hi
>
> I discussed this on #svn, and it was said that I would not like the
> answer to this but I'm gonna try anyway :-).
>
> I have a local fsfs repo, which I want to allow read-only access to
> one of my friends. Unfortunately he does have access to the
> development machine and I cannot run a server on the machine, since it
> is heavily firewalled. The only way I have to export the data is over
> plain http (I have no need for secrecy with the project). I tried
> symlinking to the repo within my .public_html, but I got 301 error
> when trying to check it out. I read the FAQ on the subject, and think
> I understand why I get it, but I cannot change httpd.conf (nor do I
> really want to).
>
> While I can do all sorts of hackish ways to solve the problem
> (post-commit hook or cron job to produce directories/tarballs/emails)
> I would like to able to do checkout over http and update directly from
> it. I don't see why this should be much different than checking out
> from a local read-only fsfs repo.
>
I'm not sure how this could possibly work. By nature, apache httpd can
"deliver" normal files sitting on disk to a client over HTTP. But a
subversion repository doesn't contain normal files -- it's a database
of some type, either BDB, or a custom flatfile database. *Something*
needs to know how to interpret the database and pull files out of it.
In other words, something needs to use libsvn_repos.so and
libsvn_fs.so.
At the moment, that thing is mod_dav_svn. What's the alternative?
What else could it possibly be? What's your proposal?
Also, keep in mind that a client running 'svn checkout http://' is
issuing all sorts of WebDAV/DeltaV commands. It's not just doing a
series of GET requests, it's much more complex than that.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Feature suggestion for read-only access to fsfs repos over http
Posted by Andrew Vaughan <aj...@netspace.net.au>.
Henrik Thostrup Jensen wrote:
>
> If http dirs was mountable (well they are, but most people does not
> use Hurd/LUFS/Fuse) this would be dead easy, since the svn client
> could see it as a local directory. It just needs to told that
> accessing files over http isn't that different ;-).
>
> Performance might be an issue, however for small repos (this one is
> currently ~400K), it won't matter.
Why not get use wget to pull down the entire repository to the client.
Then your friend can can just use file:/// access.
--
Cheers
Andrew V.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Feature suggestion for read-only access to fsfs repos over http
Posted by Greg Hudson <gh...@MIT.EDU>.
On Sun, 2005-04-10 at 12:56, Henrik Thostrup Jensen wrote:
> Yes, I've tried Arch(tla) some time ago, but it made my head hurt a bit
> too much :-). I'm thinking about checking out bazaar-ng, but it looks a
> bit untested for an RCS tool though. However the author agrees with me
> that being able to have anon read-only access over plain http is a good
> idea[1].
Bazaar-ng is definitely worth following, even if it's still a toy at the
moment.
> If http dirs was mountable (well they are, but most people does not use
> Hurd/LUFS/Fuse) this would be dead easy
Most operating systems can mount a DAV filesystem, and most web servers
can serve DAV (just straight DAV, no Subversion code involved)... but
your standard cookie-cutter httpd hosting service probably isn't
configured to allow that.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Feature suggestion for read-only access to fsfs repos over http
Posted by Henrik Thostrup Jensen <ht...@cs.aau.dk>.
Hi Greg, thanks for your answer.
On Sun, 10 Apr 2005, Greg Hudson wrote:
> On Sat, 2005-04-09 at 18:41, Henrik Thostrup Jensen wrote:
>> While I can do all sorts of hackish ways to solve the problem (post-commit
>> hook or cron job to produce directories/tarballs/emails) I would like to
>> able to do checkout over http and update directly from it. I don't see why
>> this should be much different than checking out from a local read-only
>> fsfs repo.
>
> Arch does what you want here (it has a virtual
> least-common-denominator-filesystem layer, and archive storage goes
> through that layer rather than to the filesystem directly), but
> Subversion does not.
Yes, I've tried Arch(tla) some time ago, but it made my head hurt a bit
too much :-). I'm thinking about checking out bazaar-ng, but it looks a
bit untested for an RCS tool though. However the author agrees with me
that being able to have anon read-only access over plain http is a good
idea[1].
> Part of the problem is that FSFS files are indexed; Subversion does not
> read all of an FSFS file at once in order to perform an operation, but
> seeks around within them. I'm not sure if HTTP and its various
> implementations are good for that. I also suspect that network latency
> would kill your performance.
I see. It is possible to do partial GETs over HTTP; constructing a caching
layer on top of this could probably provide some reasonable perfomance,
but I don't know how much seeking and stuff Subversion does.
If http dirs was mountable (well they are, but most people does not use
Hurd/LUFS/Fuse) this would be dead easy, since the svn client could see it
as a local directory. It just needs to told that accessing files over http
isn't that different ;-).
Performance might be an issue, however for small repos (this one is
currently ~400K), it won't matter.
1. http://sourcefrog.net/weblog/software/vc/bzr/london-2004.html
Best regards, Henrik
stud.scient Henrik Thostrup Jensen
Department of Computer Science, Aalborg University
E-mail: htj -at- cs.aau.dk, WWW: http://www.cs.aau.dk/~htj/
--
"My other car is a cdr."
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Feature suggestion for read-only access to fsfs repos over http
Posted by Greg Hudson <gh...@MIT.EDU>.
On Sat, 2005-04-09 at 18:41, Henrik Thostrup Jensen wrote:
> While I can do all sorts of hackish ways to solve the problem (post-commit
> hook or cron job to produce directories/tarballs/emails) I would like to
> able to do checkout over http and update directly from it. I don't see why
> this should be much different than checking out from a local read-only
> fsfs repo.
Arch does what you want here (it has a virtual
least-common-denominator-filesystem layer, and archive storage goes
through that layer rather than to the filesystem directly), but
Subversion does not.
Part of the problem is that FSFS files are indexed; Subversion does not
read all of an FSFS file at once in order to perform an operation, but
seeks around within them. I'm not sure if HTTP and its various
implementations are good for that. I also suspect that network latency
would kill your performance.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Feature suggestion for read-only access to fsfs repos over http
Posted by Henrik Thostrup Jensen <ht...@cs.aau.dk>.
On Sun, 10 Apr 2005, John Peacock wrote:
> Henrik Thostrup Jensen wrote:
>> I have a local fsfs repo, which I want to allow read-only access to one of
>> my friends. Unfortunately he does have access to the development
> Is this a typo? ^^^^
Yes, sorry.
>> machine and I cannot run a server on the machine, since it is heavily
>> firewalled.
>
> If he _does_ have a way to access to the dev machine (i.e. it is isn't
> completely firewalled), you can use svnserve from your own account and still
> give him readonly access.
The only export way i have is plain http :-/.
> The other way to do this is to use SVK locally, and push the project changes
> to a remote repository on your friend's system. I won't go over that method
> in detail unless that seems practical...
I think I'll use a very simple tarball system for now :-)
Best regards, Henrik
stud.scient Henrik Thostrup Jensen
Department of Computer Science, Aalborg University
E-mail: htj -at- cs.aau.dk, WWW: http://www.cs.aau.dk/~htj/
--
"My other car is a cdr."
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Feature suggestion for read-only access to fsfs repos over http
Posted by John Peacock <jp...@rowman.com>.
Henrik Thostrup Jensen wrote:
> I have a local fsfs repo, which I want to allow read-only access to one
> of my friends. Unfortunately he does have access to the development
Is this a typo? ^^^^
> machine and I cannot run a server on the machine, since it is heavily
> firewalled.
If he _does_ have a way to access to the dev machine (i.e. it is isn't
completely firewalled), you can use svnserve from your own account and still
give him readonly access.
Here's how (assuming your system is running at least 1.1 and ssh is available):
1) Force readonly access to the repository by setting the following in
svnserve.conf:
auth-access=read
and adding your friend's name to the passwd file (with a null passwd).
2) Add your friend's public key to your .ssh/authorized_keys file in a line that
looks like this:
command="svnserve --tunnel --tunnel-user friend" ssh-rsa AAAAB3NzaC1...key...
(you may need to also use the --root option to point the svnserve to the local
repository). This will allow your friend to login _as you_ but only to be able
to read the repository. Note that he have to use something like the following
lines to connect to the repository:
export SVN_SSH='ssh -l youruser'
svn ls svn+ssh://yourhost/repos/project
You now won't be able to use svn+ssh:// yourself (since you've now made all
access via svnserve be readonly), but I don't think that is a problem for you,
since you can access it using file://.
The other way to do this is to use SVK locally, and push the project changes to
a remote repository on your friend's system. I won't go over that method in
detail unless that seems practical...
John
p.s. why isn't this documented in the FAQ or better yet in Chapter 6? Are
patches welcome to add this?
--
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4720 Boston Way
Lanham, MD 20706
301-459-3366 x.5010
fax 301-429-5747
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org