Is there a way to use HTTP Auth around the full integrity server and also use the Github post commit hooks? For instance, I want my whole integrity installation to be private, and as such, I'd like to wrap the whole thing in HTTP Auth via Rack. Can I do this and still enable the /github/:token post commit features? I dont really see how github would get around the HTTP auth issue, but I figured I'd ask. Thanks - Craig
Just drop Rack::Auth::Basic into the rackup. http://github.com/rack/rack/blob/master/example/protectedlobster.ru On Tue, Mar 2, 2010 at 1:56 PM, Craig Jolicoeur <cpjolicoeur@gmail.com>wrote: > Is there a way to use HTTP Auth around the full integrity server and > also use the Github post commit hooks? > > For instance, I want my whole integrity installation to be private, > and as such, I'd like to wrap the whole thing in HTTP Auth via Rack. > > Can I do this and still enable the /github/:token post commit > features? I dont really see how github would get around the HTTP auth > issue, but I figured I'd ask. > > Thanks > > - Craig >
Maybe I didn't explain what I was wanting to do fully. I know how to get HTTP auth with Rack via the rackup file fine. My question is, if I had the HTTP Auth via Rack, how does the Github push still work (and will it work)? Github doenst have the HTTP auth credentials needed to even reach the /github/:token route of the Integrity server, correct?? On Tue, Mar 2, 2010 at 1:58 PM, Nick Quaranto <nick@quaran.to> wrote: > Just drop Rack::Auth::Basic into the rackup. > http://github.com/rack/rack/blob/master/example/protectedlobster.ru > > On Tue, Mar 2, 2010 at 1:56 PM, Craig Jolicoeur <cpjolicoeur@gmail.com> > wrote: >> >> Is there a way to use HTTP Auth around the full integrity server and >> also use the Github post commit hooks? >> >> For instance, I want my whole integrity installation to be private, >> and as such, I'd like to wrap the whole thing in HTTP Auth via Rack. >> >> Can I do this and still enable the /github/:token post commit >> features? I dont really see how github would get around the HTTP auth >> issue, but I figured I'd ask. >> >> Thanks >> >> - Craig > >
Just submit it as part of the URL... http://username:password@yourintegrityinstall.com/github/secretintegritypassword On Tue, Mar 2, 2010 at 2:01 PM, Craig Jolicoeur <cpjolicoeur@gmail.com>wrote: > Maybe I didn't explain what I was wanting to do fully. > > I know how to get HTTP auth with Rack via the rackup file fine. My > question is, if I had the HTTP Auth via Rack, how does the Github push > still work (and will it work)? > > Github doenst have the HTTP auth credentials needed to even reach the > /github/:token route of the Integrity server, correct?? > > On Tue, Mar 2, 2010 at 1:58 PM, Nick Quaranto <nick@quaran.to> wrote: > > Just drop Rack::Auth::Basic into the rackup. > > http://github.com/rack/rack/blob/master/example/protectedlobster.ru > > > > On Tue, Mar 2, 2010 at 1:56 PM, Craig Jolicoeur <cpjolicoeur@gmail.com> > > wrote: > >> > >> Is there a way to use HTTP Auth around the full integrity server and > >> also use the Github post commit hooks? > >> > >> For instance, I want my whole integrity installation to be private, > >> and as such, I'd like to wrap the whole thing in HTTP Auth via Rack. > >> > >> Can I do this and still enable the /github/:token post commit > >> features? I dont really see how github would get around the HTTP auth > >> issue, but I figured I'd ask. > >> > >> Thanks > >> > >> - Craig > > > > >
ahh, good point. didnt even think of that. thanks On Tue, Mar 2, 2010 at 2:06 PM, Nick Quaranto <nick@quaran.to> wrote: > Just submit it as part of the URL... > http://username:password@yourintegrityinstall.com/github/secretintegritypassword > > On Tue, Mar 2, 2010 at 2:01 PM, Craig Jolicoeur <cpjolicoeur@gmail.com> > wrote: >> >> Maybe I didn't explain what I was wanting to do fully. >> >> I know how to get HTTP auth with Rack via the rackup file fine. My >> question is, if I had the HTTP Auth via Rack, how does the Github push >> still work (and will it work)? >> >> Github doenst have the HTTP auth credentials needed to even reach the >> /github/:token route of the Integrity server, correct?? >> >> On Tue, Mar 2, 2010 at 1:58 PM, Nick Quaranto <nick@quaran.to> wrote: >> > Just drop Rack::Auth::Basic into the rackup. >> > http://github.com/rack/rack/blob/master/example/protectedlobster.ru >> > >> > On Tue, Mar 2, 2010 at 1:56 PM, Craig Jolicoeur <cpjolicoeur@gmail.com> >> > wrote: >> >> >> >> Is there a way to use HTTP Auth around the full integrity server and >> >> also use the Github post commit hooks? >> >> >> >> For instance, I want my whole integrity installation to be private, >> >> and as such, I'd like to wrap the whole thing in HTTP Auth via Rack. >> >> >> >> Can I do this and still enable the /github/:token post commit >> >> features? I dont really see how github would get around the HTTP auth >> >> issue, but I figured I'd ask. >> >> >> >> Thanks >> >> >> >> - Craig >> > >> > > >