Oh, ok I understand, thanx for the support :)

Regards

Il giorno martedì 6 maggio 2014 14:22:28 UTC+2, Sytse Sijbrandij ha scritto:
>
> Other ways probably mean modifications to GitLab that will make it 
> hard to upgrade. 
>
> On Tue, May 6, 2014 at 1:30 PM, Franco Tampieri 
> <fra...@tampieri.info<javascript:>> 
> wrote: 
> > mmm... is that the only way? 
> > 
> > Il giorno martedì 6 maggio 2014 12:03:45 UTC+2, Sytse Sijbrandij ha 
> scritto: 
> >> 
> >> Consider using system hooks and a small webservice for this 
> >> http://doc.gitlab.com/ce/api/system_hooks.html - 
> >> private<http://doc.gitlab.com/ce/api/system_hooks.html>- private 
> >> 
> >> On Tue, May 6, 2014 at 10:57 AM, Franco Tampieri <fra...@tampieri.info> 
>
> >> wrote: 
> >> > Hi Sytse! 
> >> > 
> >> > I know gitlab use http/s or ssh to share repository, but I've 
> configured 
> >> > the 
> >> > git-daemon package to share the internal repository as read-only 
> without 
> >> > password, and it work like charm, but I have to manually create in 
> the 
> >> > root 
> >> > of all new repository a empty file "git-daemon-export-ok", so my 
> >> > questions 
> >> > is: is possible via gitlab-shell automate the creation of that file 
> in 
> >> > every 
> >> > repository on creation? 
> >> > 
> >> > Regards 
> >> > 
> >> > Franco 
> >> > 
> >> > Il giorno martedì 6 maggio 2014 09:45:31 UTC+2, Sytse Sijbrandij ha 
> >> > scritto: 
> >> >> 
> >> >> I don't understand what you are trying to do, but in general GitLab 
> >> >> doesn't support git://, only git over http(s) and ssh. 
> >> >> 
> >> >> On Tue, May 6, 2014 at 9:11 AM, Franco Tampieri <
> fra...@tampieri.info> 
> >> >> wrote: 
> >> >> > Hi, 
> >> >> > 
> >> >> > we sharing the repository as read-only with the git:// protocol 
> for 
> >> >> > old 
> >> >> > project deploy compatibility. I would like to know how can create 
> >> >> > that 
> >> >> > file 
> >> >> > on project creation, at the moment I have to manually create that 
> >> >> > file 
> >> >> > to 
> >> >> > export project via git:// 
> >> >> > 
> >> >> > Regards 
> >> >> > 
> >> >> > Franco 
> >> >> > 
> >> >> > -- 
> >> >> > You received this message because you are subscribed to the Google 
> >> >> > Groups 
> >> >> > "GitLab" group. 
> >> >> > To unsubscribe from this group and stop receiving emails from it, 
> >> >> > send 
> >> >> > an 
> >> >> > email to gitlabhq+u...@googlegroups.com. 
> >> >> > For more options, visit https://groups.google.com/d/optout - 
> private <https://groups.google.com/d/optout> - private. 
> >> > 
> >> > -- 
> >> > You received this message because you are subscribed to the Google 
> >> > Groups 
> >> > "GitLab" group. 
> >> > To unsubscribe from this group and stop receiving emails from it, 
> send 
> >> > an 
> >> > email to gitlabhq+u...@googlegroups.com. 
> >> > For more options, visit https://groups.google.com/d/optout - 
> >> > private<https://groups.google.com/d/optout>- private. 
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> Groups 
> > "GitLab" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> an 
> > email to gitlabhq+u...@googlegroups.com <javascript:>. 
> > For more options, visit https://groups.google.com/d/optout - 
> > private<https://groups.google.com/d/optout>. 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"GitLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to gitlabhq+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to