Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
[Taking this onto the htdig-dev list, as it may be of interest to other
According to Lachlan Andrew:
> On Wed, 17 Mar 2004 05:21, Neal Richter wrote:
> > > And that leaves our "dogfood," that is our htdig databases of
> > > http://www.htdig.org and related. This occupies ~474MB:
> > > 484752 htdig
> > I assume we have compression enabled?
> The web site still uses 3.1.6, which I think doesn't support
Not for the word database, but it does support compression for the
excerpts in db.docdb. I thought it was on by default, but it appears
I was mistaken. So, no, I don't believe we have compression enabled,
but I don't know how much space we'd save by doing so.
> > >Of that, 226MB is in htdocs, including our extensive
> > >mailing list archives: 230932 htdocs
> > This is a stupid question, but where to I point SSH to get to our
> > stuff?
> No, that's a Very Good Question... A stupid question would be "How do
> I use ssh with their new-fangled authentication system?", which is
> what I'm still struggling with :)
Well, personally, I don't think either is a stupid question. The man
pages on ssh and ssh-keygen aren't exactly newbie-friendly. Myself, I
only learned enough to get by.
To answer Neal's question first, though, you point ssh to shell.sf.net,
and login using your SF.net user name and password.
You should read the SF.net document E5: Guide to generating, posting and
using SSH keys
After generating your key, you can take the contents of the id_rsa.pub
or id_dsa.pub file in your .ssh directory (on your system) and append
it to the .ssh/authorized_keys on shell.sf.net, so you can login there
without needing a password. That same key is the one you'll need to
add to the list of ssh keys on your SF.net account maintenance page to
get CVS access. See http://sourceforge.net/account/
Hope this helps.
Gilles R. Detillieux E-mail: <grdetil@...>
Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/
Dept. Physiology, U. of Manitoba Winnipeg, MB R3E 3J7 (Canada)
> > The web site still uses 3.1.6, which I think doesn't support
> > compression.
> Not for the word database, but it does support compression for the
> excerpts in db.docdb. I thought it was on by default, but it appears
> I was mistaken. So, no, I don't believe we have compression enabled,
> but I don't know how much space we'd save by doing so.
The old buggy compressor is about an 8-1 compression margin. Using
3.2.0 we are only about 3-1, but gzip based is so far much less buggy.
So how about we move to 3.2.0 on our webserver?
> To answer Neal's question first, though, you point ssh to shell.sf.net,
> and login using your SF.net user name and password.
Looks like our project is here once you get in:
FYI: I committed the libhtdigphp code last week.
RightNow Technologies, Inc.
Customer Service for Every Web Site