[gitorious] http protocol option broke

2012-07-31 Thread Rich Kucera
Hello,

Newbie question here.

Background:
We're trying to adopt git,  enterprise inhouse,   with gitorious stack from 
bitnami (saved a lot of work...).
ssh works fine,   git protocol does not due to firewall and that's ok (I 
proved it works on my laptop).
Because of some internal partitioning,   we can't ssh in both directions.
This is OK,  because I can still push the repositories in one direction for 
deployments.  That's the last option.
Well rsync push was the last option tried,  but git is now perceived as 
"partially working".

Problem:
HTTP protocol does not work in any case.   It says "you appear to have 
cloned an empty repository"
when I know there is stuff in the repository.   If I had http,  then 
presumably there'd be a pull option for deployment
in addition to the single push option I have left.

I set up my alias in /etc/hosts,  and run this:

$ git clone http://git.my.real.server.org/repoorg/repoorg.git test9876
Initialized empty Git repository in /opt/tmp/test9876/.git/
warning: You appear to have cloned an empty repository.

Have fiddled around with this and explored the source a bit,  googled, 
 nothing.  Is this a common problem?

Thanks!
Rich
p.s.
I am considering running TeamForge in a virtualbox to see how it feels in 
comparison,  but would like to stick with
gitorious if I could understand it (though I am not a Rails developer have 
got the rails training and the tshirt).

-- 
To post to this group, send email to gitorious@googlegroups.com
To unsubscribe from this group, send email to
gitorious+unsubscr...@googlegroups.com


[gitorious] Gitorious HTTPS Webhooks

2012-07-31 Thread cajadas
Hey, my Jenkins instance provider requires HTTPS + Basic Auth for webhooks 
but as i was trying to add a webhook to gitorious, it was rejected by the 
model. Is this feature enabled on earlier version? Is there a work around?

Thanks. 

-- 
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] Gitorious HTTPS Webhooks

2012-07-31 Thread Marius Mårnes Mathiesen
On Mon, Jul 30, 2012 at 7:57 PM, cajadas wrote:

> Hey, my Jenkins instance provider requires HTTPS + Basic Auth for webhooks
> but as i was trying to add a webhook to gitorious, it was rejected by the
> model. Is this feature enabled on earlier version? Is there a work around?
>

Ah, that makes a lot of sense; the only workaround I could think of is to
embed the username/password in the URL (http://user:pass@host/url) but I
don't know if that would work.

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] http protocol option broke

2012-07-31 Thread Marius Mårnes Mathiesen
On Mon, Jul 30, 2012 at 4:33 PM, Rich Kucera wrote:

> Background:
> We're trying to adopt git,  enterprise inhouse,   with gitorious stack
> from bitnami (saved a lot of work...).
> ssh works fine,   git protocol does not due to firewall and that's ok (I
> proved it works on my laptop).
> Because of some internal partitioning,   we can't ssh in both directions.
> This is OK,  because I can still push the repositories in one direction
> for deployments.  That's the last option.
> Well rsync push was the last option tried,  but git is now perceived as
> "partially working".
>
> Problem:
> HTTP protocol does not work in any case.   It says "you appear to have
> cloned an empty repository"
> when I know there is stuff in the repository.   If I had http,  then
> presumably there'd be a pull option for deployment
> in addition to the single push option I have left.
>

Rich,
Did you set up modxsendfile on the server and point this to the correct
location? Gitorious assumes this Apache module is installed and configured
so it intercepts headers like "X-Sendfile: " pointing to the path where the
git repository resides on disk.

There's a page on the wiki outlining this and other components in Gitorious
here:
https://gitorious.org/gitorious/pages/GitoriousComponents#HTTP+cloning++

 _Marius


>
> I set up my alias in /etc/hosts,  and run this:
>
> $ git clone http://git.my.real.server.org/repoorg/repoorg.git test9876
> Initialized empty Git repository in /opt/tmp/test9876/.git/
> warning: You appear to have cloned an empty repository.
>
> Have fiddled around with this and explored the source a bit,  googled,
>  nothing.  Is this a common problem?
>
> Thanks!
> Rich
> p.s.
> I am considering running TeamForge in a virtualbox to see how it feels in
> comparison,  but would like to stick with
> gitorious if I could understand it (though I am not a Rails developer have
> got the rails training and the tshirt).
>
> --
> To post to this group, send email to gitorious@googlegroups.com
> To unsubscribe from this group, send email to
> gitorious+unsubscr...@googlegroups.com
>



-- 
Marius Mårnes Mathiesen
Gitorious
Tel.: (+47) 92 60 95 38.

http://gitorious.com/

-- 
To post to this group, send email to gitorious@googlegroups.com
To unsubscribe from this group, send email to
gitorious+unsubscr...@googlegroups.com


[gitorious] Re: LDAP Authentication

2012-07-31 Thread Kevin Pelletier
No I haven't. Still same error message 

On Friday, April 20, 2012 7:12:12 PM UTC-4, beepy wrote:
>
> Did you ever get this solved?
>
> Ben,
>
> On Wednesday, 16 November 2011 11:00:48 UTC-8, Kevin Pelletier wrote:
>>
>> Hi, 
>>
>> I've been trying out lately the latest feature with LDAP 
>> Authentication. I'm not that much used to the ruby environment so 
>> excuse my missing knowledge if this looks like an easy question. When 
>> I try to test the LDAP connection, this is the error I get : 
>>
>> /home/git/gitorious/vendor/rails/activesupport/lib/active_support/ 
>> dependencies.rb:443:in `load_missing_constant': uninitialized constant 
>> SampleCallback (NameError) 
>> from /home/git/gitorious/vendor/rails/activesupport/lib/ 
>> active_support/dependencies.rb:80:in `const_missing' 
>> from /home/git/gitorious/vendor/rails/activesupport/lib/ 
>> active_support/dependencies.rb:92:in `const_missing' 
>> from /home/git/gitorious/vendor/rails/activesupport/lib/ 
>> active_support/inflector.rb:361:in `constantize' 
>> from /home/git/gitorious/vendor/rails/activesupport/lib/ 
>> active_support/inflector.rb:360:in `each' 
>> from /home/git/gitorious/vendor/rails/activesupport/lib/ 
>> active_support/inflector.rb:360:in `constantize' 
>> from /home/git/gitorious/vendor/rails/activesupport/lib/ 
>> active_support/core_ext/string/inflections.rb:162:in `constantize' 
>> from /home/git/gitorious/lib/gitorious/authentication/ 
>> ldap_authentication.rb:44:in `setup_attributes' 
>> from /home/git/gitorious/lib/gitorious/authentication/ 
>> ldap_authentication.rb:28:in `initialize' 
>> from /home/git/gitorious/lib/gitorious/authentication/ 
>> configuration.rb:41:in `new' 
>> from /home/git/gitorious/lib/gitorious/authentication/ 
>> configuration.rb:41:in `add_custom_method' 
>> from /home/git/gitorious/lib/gitorious/authentication/ 
>> configuration.rb:24:in `configure' 
>> from /home/git/gitorious/lib/gitorious/authentication/ 
>> configuration.rb:24:in `each' 
>> from /home/git/gitorious/lib/gitorious/authentication/ 
>> configuration.rb:24:in `configure' 
>> from /home/git/gitorious/config/initializers/authentication.rb: 
>> 23 
>> from /home/git/gitorious/vendor/rails/activesupport/lib/ 
>> active_support/dependencies.rb:147:in 
>> `load_without_new_constant_marking' 
>> from /home/git/gitorious/vendor/rails/activesupport/lib/ 
>> active_support/dependencies.rb:147:in `load' 
>> from /home/git/gitorious/vendor/rails/railties/lib/ 
>> initializer.rb:622:in `load_application_initializers' 
>> from /home/git/gitorious/vendor/rails/railties/lib/ 
>> initializer.rb:621:in `each' 
>> from /home/git/gitorious/vendor/rails/railties/lib/ 
>> initializer.rb:621:in `load_application_initializers' 
>> from ./config/../vendor/rails/railties/lib/initializer.rb: 
>> 176:in `process' 
>> from ./config/../vendor/rails/railties/lib/initializer.rb: 
>> 113:in `send' 
>> from ./config/../vendor/rails/railties/lib/initializer.rb: 
>> 113:in `run' 
>> from ./config/environment.rb:24 
>> from script/test_ldap_connection:8:in `require' 
>> from script/test_ldap_connection:8 
>>
>> Any ideas why I get this error message? 
>>
>> Thank you 
>>
>> Kevin
>
>

-- 
To post to this group, send email to gitorious@googlegroups.com
To unsubscribe from this group, send email to
gitorious+unsubscr...@googlegroups.com


[gitorious] Adding functionality to repository creation

2012-07-31 Thread Rachel Harris
I would like to have a default file get generated in every new repo that is 
created by users of my Gitorious installation. I think I'm pretty clear on 
the code to do this (i.e. using Repository.git.add, etc...). My problem is 
figuring out *where* to put this code.

I know I can't put my code into the creation of the repository object (e.g. 
with an after_create method in Repository) because the actual repo creation 
is done asynchronously by stompserver. 
Repository.post_repo_creation_message appears to set things up so that 
Repository.create_git_repository will be executed by stompserver, but my 
testing so far shows that Repository.create_git_repository is never being 
called, even though the repositories are being generated just fine.

What am I not seeing here?

-- 
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] Re: LDAP Authentication

2012-07-31 Thread Marius Mårnes Mathiesen
Kevin,
Would you mind trying to check out the features/ldap_authorization branch
from mainline and see how it works there? There's quite a lot of new stuff
in there, and I think there's a fix to the error message you're seeing as
well.


Cheers,
- Marius

On Tue, Jul 31, 2012 at 9:19 PM, Kevin Pelletier
wrote:

> No I haven't. Still same error message
>
>
> On Friday, April 20, 2012 7:12:12 PM UTC-4, beepy wrote:
>>
>> Did you ever get this solved?
>>
>> Ben,
>>
>> On Wednesday, 16 November 2011 11:00:48 UTC-8, Kevin Pelletier wrote:
>>>
>>> Hi,
>>>
>>> I've been trying out lately the latest feature with LDAP
>>> Authentication. I'm not that much used to the ruby environment so
>>> excuse my missing knowledge if this looks like an easy question. When
>>> I try to test the LDAP connection, this is the error I get :
>>>
>>> /home/git/gitorious/vendor/**rails/activesupport/lib/**active_support/
>>> dependencies.rb:443:in `load_missing_constant': uninitialized constant
>>> SampleCallback (NameError)
>>> from /home/git/gitorious/vendor/**rails/activesupport/lib/
>>> active_support/dependencies.**rb:80:in `const_missing'
>>> from /home/git/gitorious/vendor/**rails/activesupport/lib/
>>> active_support/dependencies.**rb:92:in `const_missing'
>>> from /home/git/gitorious/vendor/**rails/activesupport/lib/
>>> active_support/inflector.rb:**361:in `constantize'
>>> from /home/git/gitorious/vendor/**rails/activesupport/lib/
>>> active_support/inflector.rb:**360:in `each'
>>> from /home/git/gitorious/vendor/**rails/activesupport/lib/
>>> active_support/inflector.rb:**360:in `constantize'
>>> from /home/git/gitorious/vendor/**rails/activesupport/lib/
>>> active_support/core_ext/**string/inflections.rb:162:in `constantize'
>>> from /home/git/gitorious/lib/**gitorious/authentication/
>>> ldap_authentication.rb:44:in `setup_attributes'
>>> from /home/git/gitorious/lib/**gitorious/authentication/
>>> ldap_authentication.rb:28:in `initialize'
>>> from /home/git/gitorious/lib/**gitorious/authentication/
>>> configuration.rb:41:in `new'
>>> from /home/git/gitorious/lib/**gitorious/authentication/
>>> configuration.rb:41:in `add_custom_method'
>>> from /home/git/gitorious/lib/**gitorious/authentication/
>>> configuration.rb:24:in `configure'
>>> from /home/git/gitorious/lib/**gitorious/authentication/
>>> configuration.rb:24:in `each'
>>> from /home/git/gitorious/lib/**gitorious/authentication/
>>> configuration.rb:24:in `configure'
>>> from /home/git/gitorious/config/**initializers/authentication.**rb:
>>>
>>> 23
>>> from /home/git/gitorious/vendor/**rails/activesupport/lib/
>>> active_support/dependencies.**rb:147:in
>>> `load_without_new_constant_**marking'
>>> from /home/git/gitorious/vendor/**rails/activesupport/lib/
>>> active_support/dependencies.**rb:147:in `load'
>>> from /home/git/gitorious/vendor/**rails/railties/lib/
>>> initializer.rb:622:in `load_application_**initializers'
>>> from /home/git/gitorious/vendor/**rails/railties/lib/
>>> initializer.rb:621:in `each'
>>> from /home/git/gitorious/vendor/**rails/railties/lib/
>>> initializer.rb:621:in `load_application_**initializers'
>>> from ./config/../vendor/rails/**railties/lib/initializer.rb:
>>> 176:in `process'
>>> from ./config/../vendor/rails/**railties/lib/initializer.rb:
>>> 113:in `send'
>>> from ./config/../vendor/rails/**railties/lib/initializer.rb:
>>> 113:in `run'
>>> from ./config/environment.rb:24
>>> from script/test_ldap_connection:8:**in `require'
>>> from script/test_ldap_connection:8
>>>
>>> Any ideas why I get this error message?
>>>
>>> Thank you
>>>
>>> Kevin
>>
>>  --
> To post to this group, send email to gitorious@googlegroups.com
> To unsubscribe from this group, send email to
> gitorious+unsubscr...@googlegroups.com
>



-- 
Marius Mårnes Mathiesen
Gitorious
Tel.: (+47) 92 60 95 38.

http://gitorious.com/

-- 
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] Adding functionality to repository creation

2012-07-31 Thread Marius Mårnes Mathiesen
On Tue, Jul 31, 2012 at 7:54 PM, Rachel Harris  wrote:

> I would like to have a default file get generated in every new repo that
> is created by users of my Gitorious installation. I think I'm pretty clear
> on the code to do this (i.e. using Repository.git.add, etc...). My problem
> is figuring out *where* to put this code.
>
> I know I can't put my code into the creation of the repository object
> (e.g. with an after_create method in Repository) because the actual repo
> creation is done asynchronously by stompserver.
> Repository.post_repo_creation_message appears to set things up so that
> Repository.create_git_repository will be executed by stompserver, but my
> testing so far shows that Repository.create_git_repository is never being
> called, even though the repositories are being generated just fine.
>

Rachel,
Here's roughly how it works:
- After a repository is created, `post_repo_creation_message` is called
- This will send a message to the message queue, containing (among other
things) the command to be run: `create_git_repository`
- This message is picked up by
app/processors/repository_creation_processor.rb, which will actually
perform Repository.create_git_repository

Repository.create_git_repository will:
- create the repository on disk
- create the hooks required by Gitorious (it will create a symlink to the
shared hooks directory in Gitorious)

This would probably be a natural place to add your code.

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