Re: [gitorious] Diagnostics questions
On Tue, Oct 23, 2012 at 03:20:05PM +0800, Bas Vodde wrote: > > Hiya, > > We've been upgrading our own gitorious installation to the latest and have > used the diagnostics to try to find things that could be improved. I've got a > question about this: > > The diagnostics failed on: "hostname not bound to a 'git.*' subdomain?" > > Our gitorious installation is at git.companyname.com. > > Why isn't it ok to have the hostname be git.* ? (we've not had any problem > with this) This will cause Gitorious to interpret all requests to be git-over-http requests (these are identified by the fqdn used in the request). IIRC, this means that all requests are processed by the "metal" which serves git over HTTP, but as the requests don't look like Git requests they will (probably) be passed on to the "regular" Rails app. Cheers, - Marius -- To post to this group, send email to gitorious@googlegroups.com To unsubscribe from this group, send email to gitorious+unsubscr...@googlegroups.com
Re: [gitorious] error "nil_class_path" when creating a new group (private install)
On Mon, Oct 22, 2012 at 11:25:07PM -0700, Goulou wrote:
> Hi All,
>
> Whenever I try to create a new group (or team), be it as a normal user or
> as an administrator, after a pretty long load time, I get the page "Sorry,
> something went wrong".
> In details, the error is :
> A ActionView::TemplateError occurred in groups#create :
>
> undefined method "nil_class_path" for #
> On line #23 of app/views/groups/new.html.erb
>
> The line in question is the following :
> <% form_for @group, :html => {:multipart => true} do |f| -%>
>
> If necessary I may provide a backtrace, but the server is not directly
> available at the moment.
>
> This problem is really a blocker for me, and I'll be very thankful if you
> can provide me of some help!
Looks like creating the group failed, causing the controller to throw
either an ActiveRecord::RecordInvalid or ActiveRecord::RecordNotFound
error. This will cause the form to be re-rendered. In this case,
@group should be the group you just tried to create, but it seems to
be nil.
Are you running with LDAP integration? Any other special settings?
Cheers,
- Marius
--
To post to this group, send email to gitorious@googlegroups.com
To unsubscribe from this group, send email to
gitorious+unsubscr...@googlegroups.com
Re: [gitorious] problem cloning repo via https access
hi, I have tried now random repos and didn't find one where it's working So either it is not working from beginning or the error hits all repos sooner or later. what is funny, ist that pulls work fine after an initial clone via git: It is enough to copy .git directory and change the url in config to https After this a git reset --hard does the trick ... maybe it is worth to look into this or just have a note that http clone is not working as intended to spare others frustration thanks On Thursday, October 18, 2012 10:21:20 AM UTC+2, Marius Mårnes Mathiesen wrote: > > On Thu, Oct 18, 2012 at 12:45:08AM -0700, schufti wrote: > > Hi, > > some time in the past I must have been able to clone repos via https > since > > my dev. machine is behind a natting firewall-proxy allowing http(s) > access > > only. And up to now I didn't experience any problem pulling from these > > repos. But recently I had to clone a repo to a new machine and suddenly > I > > was presented with the following message: > > > > git clone https://git.gitorious.org/neutrino-hd/buildsystem-cs.gitseife > > > Cloning into 'seife'... > > > warning: remote HEAD refers to nonexistent ref, unable to checkout. > > The issue here is that our Git-over-HTTP service uses the "dumb" HTTP > protocol; which pulls down commits one by one. The first thing that > this service does is to try to locate the HEAD of the repository; > which should point to a valid ref (branch). It looks like the HEAD > reference on this repository points to a non-existing ref. > > The owner of the repository should be able to change which branch HEAD > points to in the repository using the Gitorious UI. > > > -- > > Cheers, > - Marius > -- To post to this group, send email to gitorious@googlegroups.com To unsubscribe from this group, send email to gitorious+unsubscr...@googlegroups.com
Re: [gitorious] problem cloning repo via https access
hi, I have tried now random repos and didn't find one where it's working So either it is not working from beginning or the error hits all repos sooner or later. what is funny, ist that pulls work fine after an initial clone via git: It is enough to copy .git directory and change the url in config to https After this a git reset --hard does the trick ... maybe it is worth to look into this or just have a note that http clone is not working as intended to spare others frustration thanks On Thursday, October 18, 2012 7:20:13 PM UTC+2, schufti wrote: > > Hi, > thank you for the quick answer that I forwarded to the repo owner. > > Unfortunately it didn't change the situation. He reported that HAED points > to MASTER and there are no branches in his repo. > > Any other ideas what might be wrong or how to fix this? > > > Am Donnerstag, 18. Oktober 2012 10:21:20 UTC+2 schrieb Marius Mårnes > Mathiesen: >> >> On Thu, Oct 18, 2012 at 12:45:08AM -0700, schufti wrote: >> > Hi, >> > some time in the past I must have been able to clone repos via https >> since >> > my dev. machine is behind a natting firewall-proxy allowing http(s) >> access >> > only. And up to now I didn't experience any problem pulling from these >> > repos. But recently I had to clone a repo to a new machine and suddenly >> I >> > was presented with the following message: >> > >> > git clone https://git.gitorious.org/neutrino-hd/buildsystem-cs.gitseife >> > > Cloning into 'seife'... >> > > warning: remote HEAD refers to nonexistent ref, unable to checkout. >> >> The issue here is that our Git-over-HTTP service uses the "dumb" HTTP >> protocol; which pulls down commits one by one. The first thing that >> this service does is to try to locate the HEAD of the repository; >> which should point to a valid ref (branch). It looks like the HEAD >> reference on this repository points to a non-existing ref. >> >> The owner of the repository should be able to change which branch HEAD >> points to in the repository using the Gitorious UI. >> >> >> -- >> >> Cheers, >> - Marius >> > -- To post to this group, send email to gitorious@googlegroups.com To unsubscribe from this group, send email to gitorious+unsubscr...@googlegroups.com
