I'm trying to get gitorious up and running on forkolator.org. Things
are going well, the front end is working, I figured out the task
queue, etc. I'm stuck on a problem though:
When I try to push some changes up to my server, instead of asking for
the passphrase for my key, it asks me for g...@forkolator.org's
password. I'm running the git daemon as root (I know, maybe a bad
idea?) by running script/git-daemon. And it looks like my public key
is in /root/.ssh/authorized_keys. That file looks like:
I can push just fine to gitorious.org with the same key, so it must be
something wrong with my server configuration. Does anyone have any
ideas what might be going wrong?
Or failing that... can anyone give me some guidance on where to look
debugging-wise? I've spent most of the day poking around and haven't
had much luck. My best guess is that it has something to do with
what's happening in the strainer class, and the SSH module, but I'm
not sure.
On Thu, May 8, 2008 at 2:09 AM, Erik Pukinskis <erikpukins...@gmail.com> wrote:
> Hello,
> I'm trying to get gitorious up and running on forkolator.org. Things > are going well, the front end is working, I figured out the task > queue, etc. I'm stuck on a problem though:
> When I try to push some changes up to my server, instead of asking for > the passphrase for my key, it asks me for g...@forkolator.org's > password. I'm running the git daemon as root (I know, maybe a bad > idea?) by running script/git-daemon. And it looks like my public key > is in /root/.ssh/authorized_keys. That file looks like:
> I can push just fine to gitorious.org with the same key, so it must be > something wrong with my server configuration. Does anyone have any > ideas what might be going wrong?
> Or failing that... can anyone give me some guidance on where to look > debugging-wise? I've spent most of the day poking around and haven't > had much luck. My best guess is that it has something to do with > what's happening in the strainer class, and the SSH module, but I'm > not sure.
First off, don't run it as root. Really.
OK, so the git-daemon is for the git:// protocol only, you can't push to it. Pushing is done over SSH. So, the command="gitorious erik" part of the publickey entry is the one that does some sanity and permission checking (aborting early if it fails), by running the gitorious bin (so it needs to be somewhere in the ssh daemons $PATH, I symlink mine from RAILS_ROOT/script/gitorious to /bin/gitorious), and passed your username (which in turn is coupled to the publickey following it) and the path to the repos you want to push to. It checks permissions by asking the app for it, or aborts or gives the a-ok if everything is fine.
By the way, I hope you'll be able to contribute back to Gitorious, it's kinda weird there's already two forks (the other being "appcast"), when I still consider gitorious to be pretty early on feature wise. :)
> OK, so the git-daemon is for the git:// protocol only, you can't push
> to it. Pushing is done over SSH. So, the command="gitorious erik" part
> of the publickey entry is the one that does some sanity and permission
> checking (aborting early if it fails), by running the gitorious bin
> (so it needs to be somewhere in the ssh daemons $PATH, I symlink mine
> from RAILS_ROOT/script/gitorious to /bin/gitorious), and passed your
> username (which in turn is coupled to the publickey following it) and
> the path to the repos you want to push to. It checks permissions by
> asking the app for it, or aborts or gives the a-ok if everything is
> fine.
Aahhhhh! That makes sense. That's working now, thanks! I've been
keeping track of everything that needs to be done to set up Gitorious
and it's posted here:
I'll add that stuff to the HACKING file as soon as I figure out the
ultrasphinx stuff and graph_generator, and the other bits and pieces I
have left to configure.
> By the way, I hope you'll be able to contribute back to Gitorious,
> it's kinda weird there's already two forks (the other being
> "appcast"), when I still consider gitorious to be pretty early on
> feature wise. :)
Yeah, I'd love not to fork Gitorious, and keep our source trees
synced, or at least keep them compatible with one another. The only
reason to fork would be if you decide you don't want to use some of
the stuff I implement.
Anyway, thanks for writing all this great code for us to work with!
And sorry for the spam from running the Rspec tests. I changed the
email address in my tree so it goes to me instead of you. I wonder if
there's some way to have a TEST_EMAIL setting in gitorious.yml and use
that instead of hard-coding your email address into the fixtures.
On Sun, May 11, 2008 at 4:22 PM, Erik Pukinskis <erikpukins...@gmail.com> wrote: > email address in my tree so it goes to me instead of you. I wonder if > there's some way to have a TEST_EMAIL setting in gitorious.yml and use > that instead of hard-coding your email address into the fixtures.
There's no reason to send out emails in the test (or development) environment. That's the default too, so you must've changed it.
|
