OK, I did setup an A record on our name server for git.myserver.com and then deployed gitorious to Apache2 via Passenger. And now it works, at least, using SSH URL. I can clone and push back. This is great. But if anyone can advise me on local setup in my case, that would be really helpful too!
On Aug 24, 8:20 am, Aleksej Nesterow <[email protected]> wrote: > Forgot to say. Here is the gitorious_auth.log output: > > I, [2011-08-23 21:51:13#2423] INFO -- : Connection from "192.168.1.33 > 60478 22" (aleks): git-receive-pack 'mainline/mainline.git' > I, [2011-08-23 21:51:13#2423] INFO -- : Access denied or bad > repository path for "aleks": "git-receive-pack 'mainline/ > mainline.git'" > > And production.log is empty. > > On Aug 23, 10:11 pm, Aleksej Nesterow <[email protected]> > wrote: > > > > > > > > > Hi all! > > > The subj message from Gitorious appears when I'm trying to clone or > > push the existing repo. I know, this is old. But I've read probably > > every thread in this forum regarding this issue, and couldn't resolve > > mine. > > > I'm using the SSH path copied from Gitorious web UI, so I know it > > really exists. > > > A bit about my setup. It's Ubuntu 11.04 installed on a local server. > > I'm connected to this server from a desktop under Mac OS X using ssh > > keys. To be more specific, the server is running on IP 192.168.1.37. I > > however added a record to /etc/hosts for Mac OS X, so I could type in > > browser something like: git.myserver.com:3000. I followed this > > instruction > > precisely:http://cjohansen.no/en/ruby/setting_up_gitorious_on_your_own_server > > I went the Ruby 1.8 path. Also I added git.local to /etc/hosts on my > > Ubuntu server to resolve to 127.0.0.1. > > > After I could successfully log in to gitorious, I added my public key > > from Mac OS X. Exactly the same I'm using to log into the server > > itself using ssh. Got Ready (V) status. Here is how authorized_keys > > file looks for git user on the server: > > > ### START KEY 4 ### > > command="gitorious aleks",no-port-forwarding,no-X11-forwarding,no- > > agent-forwarding,no-pty ssh-rsa SOME_KEY SshKey:4-User:1 > > ### END KEY 4 ### > > > However originally it looked like this: > > > ssh-rsa SOME_LONG_SEQUENCE [email protected] > > > Here is the gitorious config for the production environment. > > > production: > > cookie_secret: some_secret_goes_here > > > repository_base_path: "/home/git/repositories" > > gitorious_client_port: 80 > > gitorious_client_host: git.local > > gitorious_host: git.myserver.com > > gitorious_user: git > > gitorious_support_email: [email protected] > > exception_notification_emails: [email protected] > > mangle_email_addresses: true > > public_mode: true > > locale: en > > archive_cache_dir: "/var/git/tarballs" > > archive_work_dir: "/var/git/tarball-work" > > only_site_admins_can_create_projects: false > > hide_http_clone_urls: false > > use_ssl: false > > is_gitorious_dot_org: true > > terms_of_use: false > > terms_of_service_url:http://en.gitorious.org/tos > > privacy_policy_url:http://en.gitorious.org/privacy_policy > > messaging_adapter: stomp > > > The question is, how I can resolve the subj. issue assuming my setup > > above? -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected]
