Re: Fork not working gitlab-ce-8.14.3-ce.0.el7.x86_64

[T.J. Yang]

Hi Phil

Thanks for the info. I don't have fork issue since I was not using jira.
My 8.14.0 upgrade (to 8.14.4)  went fine this morning and  the forking test 
was ok.

tj

On Wednesday, December 7, 2016 at 3:46:07 PM UTC-6, Phil Evans wrote:
>
> Hi tj,
>
> I raised a bug for this issue, too. 
> https://gitlab.com/gitlab-org/gitlab-ce/issues/25390
>
> And the response from the Gitlab team was excellent.
>
> Turns out that somehow the JIRA Service Template was causing forking to 
> fail!
> So I just de-activated the Template and then forking magically started 
> working again.
> More info about the issue can be found here 
> https://gitlab.com/gitlab-org/gitlab-ce/issues/25112
>
> If you're not using that JIRA integration you should be fine.
>
> If you are there are some new fields in the template you need to fill. 
> Or you can just deactivate as I've done for now.
>
>
> Kind regards,
> Phil
>
>
>
>
>
>
>
>
>
>
> On Thursday, December 8, 2016 at 10:30:07 AM UTC+13, T.J. Yang wrote:
>>
>> Hi Phil
>>
>> I plan to do a 8.14.0 to 8.14.3 upgrade Friday.
>> I will add forking test as part of my post-upgrade test. 
>> If repo forked fail on 8.14.3 version then I will reverse back to 8.14.0.
>>
>> Thanks for the warning
>>
>> tj
>>
>> On Tuesday, December 6, 2016 at 6:48:53 PM UTC-6, Phil Evans wrote:
>>>
>>> Hi,
>>>
>>> We recently upgraded gitlab-ce to version 8.14.2.
>>> *Since that upgrade we can no longer fork projects from the GUI.*
>>>
>>> Today, I did a yum update which installed a new version 8.14.3.
>>> Unfortunately, the error is still happening.
>>>
>>> I've attached a screenshot of the failed message from the fork.
>>>
>>> As you'll see we're being told that the repository for this project does 
>>> not exist.
>>>
>>> When I look in /var/opt/gitlab/git-data/repositories/phile I can see 
>>> that a directory called gowiki.wiki.git was created for my attempted fork, 
>>> but not gowiki.git as I'd expect.
>>>
>>> If I hit the remove project button from the screen attached, the 
>>> gowiki.wiki.git directory is successfully removed.
>>>
>>> There is plenty of disk space available on the server.
>>>
>>> Server is running...
>>> Red Hat Enterprise Linux Server release 7.3 (Maipo)
>>>
>>>
>>> Thanks in advance,
>>> Phil
>>>
>>>
>>>
>>>
>>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/gitlabhq/48fc7288-620a-436b-849c-a7409b1b4707%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Fork not working gitlab-ce-8.14.3-ce.0.el7.x86_64

[T.J. Yang]

Hi Phil

I plan to do a 8.14.0 to 8.14.3 upgrade Friday.
I will add forking test as part of my post-upgrade test. 
If repo forked fail on 8.14.3 version then I will reverse back to 8.14.0.

Thanks for the warning

tj

On Tuesday, December 6, 2016 at 6:48:53 PM UTC-6, Phil Evans wrote:
>
> Hi,
>
> We recently upgraded gitlab-ce to version 8.14.2.
> *Since that upgrade we can no longer fork projects from the GUI.*
>
> Today, I did a yum update which installed a new version 8.14.3.
> Unfortunately, the error is still happening.
>
> I've attached a screenshot of the failed message from the fork.
>
> As you'll see we're being told that the repository for this project does 
> not exist.
>
> When I look in /var/opt/gitlab/git-data/repositories/phile I can see that 
> a directory called gowiki.wiki.git was created for my attempted fork, but 
> not gowiki.git as I'd expect.
>
> If I hit the remove project button from the screen attached, the 
> gowiki.wiki.git directory is successfully removed.
>
> There is plenty of disk space available on the server.
>
> Server is running...
> Red Hat Enterprise Linux Server release 7.3 (Maipo)
>
>
> Thanks in advance,
> Phil
>
>
>
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/gitlabhq/d8c5cbcd-92b0-411b-8bb9-2ec52367e564%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ldap account going through approval process ?

[T.J. Yang]

https://gitlab.com/gitlab-org/gitlab-ce/issues/25239

On Sunday, November 20, 2016 at 1:25:00 PM UTC-6, Aleksey Tsalolikhin wrote:
>
>
> On Tuesday, October 11, 2016 at 3:36:53 PM UTC-5, T.J. Yang wrote:
>>
>> Hi
>>
>> I have ldap backend server configured and one can create gitlab account 
>> automatically if the ldap account is valid.
>> Is it possible the auto-create still going through administrator's 
>> approval first then auto-create ?
>>
>
> and
>
> On Tue, Nov 15, 2016 at 1:35 PM, T.J. Yang <tjyan...@gmail.com 
> > wrote:
>
>>
>> I (as gitlab admin) am trying to gain ability to grant or deny a newly 
>> created gitlab account.
>> I also change sign-in page to info new user, extra email sending to 
>> gitlabad...@xxx.xxx for further approval.
>>
>
> Hey, T.J.   Take a look at 
> https://gitlab.com/gitlab-org/gitlab-ce/issues/14508  -- would that solve 
> your problem?  It provides a way to "gateway" access for local users. 
> (Where an admin has to approve access.)  It seems like you are asking for 
> something similar but for LDAP users.
>
> If studying 14508 doesn't help, you might want to open a similar issue, 
> e.g., "admin approval for LDAP users", or something like that.
>
> HTH,
> Aleksey
>
>  
> ᐧ
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/gitlabhq/bd23400a-9728-4a6c-aaec-5c20eebbb439%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ldap account going through approval process ?

[T.J. Yang]

Hi Aleksey

On Tuesday, November 15, 2016 at 7:42:54 AM UTC-6, Aleksey Tsalolikhin 
wrote:
>
> Sorry, tj, cold you please remind me what you are trying to accomplish?  
> Do you want anyone with an LDAP account to be able to sign up for GitLab 
> without administrator involvement?
>

I (as gitlab admin) am trying to gain ability to grant or deny a newly 
created gitlab account.
I also change sign-in page to info new user, extra email sending to 
gitlabad...@xxx.xxx for further approval.

tj 

>
> On Tue, Nov 15, 2016 at 2:43 AM, T.J. Yang <tjyan...@gmail.com 
> > wrote:
>
>> I went through a few runs of version gitlab CE since 10/15/2016.
>> Now the auto account creation is created locked mode. 
>> Administrator will need to unlock the newly created account. 
>>
>> On Saturday, October 15, 2016 at 8:40:25 AM UTC-5, Aleksey Tsalolikhin 
>> wrote:
>>>
>>> Perhaps run "sudo gitlab-ctl reconfigure" ?
>>>
>>> ᐧ
>>> On Sat, Oct 15, 2016 at 12:19 AM, T.J. Yang <tjyan...@gmail.com> wrote:
>>>
>>>> Thanks for the pointer to setting of block_auto_created_users.
>>>>
>>>> 1. set it to true and restart gilab 8.12.6
>>>>
>>>> [root@re02 ~]# grep block_auto_created_users /etc/gitlab/gitlab.rb
>>>>   block_auto_created_users: true
>>>> # block_auto_created_users: false
>>>> # gitlab_rails['omniauth_block_auto_created_users'] = true
>>>> [root@ilclsre02 ~]# gitlab-ctl restart
>>>> ok: run: gitlab-workhorse: (pid 6661) 1s
>>>> ok: run: logrotate: (pid 6673) 0s
>>>> ok: run: nginx: (pid 6679) 0s
>>>> ok: run: postgresql: (pid 6688) 1s
>>>> ok: run: redis: (pid 6698) 0s
>>>> ok: run: sidekiq: (pid 6714) 1s
>>>> ok: run: unicorn: (pid 6719) 0s
>>>> [root@re02 ~]#
>>>>
>>>> 2. Delete userA  from admin console
>>>> 3. Ask userA to login again
>>>>  3.1  step 2 and 3 are a few minutes apart. 
>>>> 4. userA was able to login and gitlab account auto recreated again.
>>>>  4.1 from userA's profile page, userA is not locked.
>>>>
>>>> So this setting is not working,
>>>>
>>>>
>>>> On Tuesday, October 11, 2016 at 3:36:53 PM UTC-5, T.J. Yang wrote:
>>>>>
>>>>> Hi
>>>>>
>>>>> I have ldap backend server configured and one can create gitlab 
>>>>> account automatically if the ldap account is valid.
>>>>>
>>>>> Is it possible the auto-create still going through administrator's 
>>>>> approval first then auto-create ?
>>>>>
>>>>>
>>>>>
>>>>> tj
>>>>>
>>>> -- 
>>>> 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.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/gitlabhq/e6361112-aa85-4d57-8ae2-1def435c0a67%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/gitlabhq/e6361112-aa85-4d57-8ae2-1def435c0a67%40googlegroups.com?utm_medium=email_source=footer>
>>>> .
>>>>
>>>> For more options, visit 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+u...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/gitlabhq/3c54a299-7a15-4e4a-9cba-42e8a9c76ea9%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/gitlabhq/3c54a299-7a15-4e4a-9cba-42e8a9c76ea9%40googlegroups.com?utm_medium=email_source=footer>
>> .
>> For more options, visit 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/gitlabhq/e773198d-c8dd-464d-aa36-1577862ec24c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ldap account going through approval process ?

[T.J. Yang]

I went through a few runs of version gitlab CE since 10/15/2016.
Now the auto account creation is created locked mode. 
Administrator will need to unlock the newly created account. 

On Saturday, October 15, 2016 at 8:40:25 AM UTC-5, Aleksey Tsalolikhin 
wrote:
>
> Perhaps run "sudo gitlab-ctl reconfigure" ?
>
> ᐧ
>
> -- 
> Need training on CFEngine, Git or Time Management?  Email 
> trai...@verticalsysadmin.com .
>
> On Sat, Oct 15, 2016 at 12:19 AM, T.J. Yang <tjyan...@gmail.com 
> > wrote:
>
>> Thanks for the pointer to setting of block_auto_created_users.
>>
>> 1. set it to true and restart gilab 8.12.6
>>
>> [root@re02 ~]# grep block_auto_created_users /etc/gitlab/gitlab.rb
>>   block_auto_created_users: true
>> # block_auto_created_users: false
>> # gitlab_rails['omniauth_block_auto_created_users'] = true
>> [root@ilclsre02 ~]# gitlab-ctl restart
>> ok: run: gitlab-workhorse: (pid 6661) 1s
>> ok: run: logrotate: (pid 6673) 0s
>> ok: run: nginx: (pid 6679) 0s
>> ok: run: postgresql: (pid 6688) 1s
>> ok: run: redis: (pid 6698) 0s
>> ok: run: sidekiq: (pid 6714) 1s
>> ok: run: unicorn: (pid 6719) 0s
>> [root@re02 ~]#
>>
>> 2. Delete userA  from admin console
>> 3. Ask userA to login again
>>  3.1  step 2 and 3 are a few minutes apart. 
>> 4. userA was able to login and gitlab account auto recreated again.
>>  4.1 from userA's profile page, userA is not locked.
>>
>> So this setting is not working,
>>
>>
>> On Tuesday, October 11, 2016 at 3:36:53 PM UTC-5, T.J. Yang wrote:
>>>
>>> Hi
>>>
>>> I have ldap backend server configured and one can create gitlab account 
>>> automatically if the ldap account is valid.
>>>
>>> Is it possible the auto-create still going through administrator's 
>>> approval first then auto-create ?
>>>
>>>
>>>
>>> tj
>>>
>> -- 
>> 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 .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/gitlabhq/e6361112-aa85-4d57-8ae2-1def435c0a67%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/gitlabhq/e6361112-aa85-4d57-8ae2-1def435c0a67%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>> For more options, visit 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/gitlabhq/3c54a299-7a15-4e4a-9cba-42e8a9c76ea9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ldap account going through approval process ?

[T.J. Yang]

Thanks for the pointer to setting of block_auto_created_users.

1. set it to true and restart gilab 8.12.6

[root@re02 ~]# grep block_auto_created_users /etc/gitlab/gitlab.rb
  block_auto_created_users: true
# block_auto_created_users: false
# gitlab_rails['omniauth_block_auto_created_users'] = true
[root@ilclsre02 ~]# gitlab-ctl restart
ok: run: gitlab-workhorse: (pid 6661) 1s
ok: run: logrotate: (pid 6673) 0s
ok: run: nginx: (pid 6679) 0s
ok: run: postgresql: (pid 6688) 1s
ok: run: redis: (pid 6698) 0s
ok: run: sidekiq: (pid 6714) 1s
ok: run: unicorn: (pid 6719) 0s
[root@re02 ~]#

2. Delete userA  from admin console
3. Ask userA to login again
 3.1  step 2 and 3 are a few minutes apart. 
4. userA was able to login and gitlab account auto recreated again.
 4.1 from userA's profile page, userA is not locked.

So this setting is not working,


On Tuesday, October 11, 2016 at 3:36:53 PM UTC-5, T.J. Yang wrote:
>
> Hi
>
> I have ldap backend server configured and one can create gitlab account 
> automatically if the ldap account is valid.
>
> Is it possible the auto-create still going through administrator's 
> approval first then auto-create ?
>
>
>
> tj
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/gitlabhq/e6361112-aa85-4d57-8ae2-1def435c0a67%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

ldap account going through approval process ?

[T.J. Yang]

Hi

I have ldap backend server configured and one can create gitlab account 
automatically if the ldap account is valid.

Is it possible the auto-create still going through administrator's approval 
first then auto-create ?



tj

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/gitlabhq/1c792fac-a493-42de-aed7-6e8fb9642718%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Can't create branches

[T.J. Yang]

On Thursday, June 23, 2016 at 6:33:37 AM UTC-5, Adriaan W. wrote:
>
> I can't create any branches in gitlab for all my repos. When i give it a 
> name and click on create, the page is loading very long and after a long 
> time I get an 502 error. I have this problem still in 8.9. A restart of 
> gitlab and the server didn't help.
>

I tested branch creation with gitlab-ce with my 8.9 instance, no problem.

[user01@server01 ws]$ git clone g...@mygit.test.com:USER01/test01.git
Cloning into 'test01'...
warning: You appear to have cloned an empty repository.
[user01@server01 ws]$ cd test01/
[user01@server01 test01]$ ls
[user01@server01 test01]$ ls
[user01@server01 test01]$ git checkout -b develop
Switched to a new branch 'develop'
[user01@server01 test01]$ touch develop.txt
[user01@server01 test01]$ echo test >> develop.txt
[user01@server01 test01]$ git add develop.txt;git commit develop.txt -m 
"adding develop.txt"
[develop (root-commit) fd16b39] adding develop.txt
 1 file changed, 1 insertion(+)
 create mode 100644 develop.txt
[user01@server01 test01]$ git push origin develop
Counting objects: 3, done.
Writing objects: 100% (3/3), 231 bytes | 0 bytes/s, done.
Total 3 (delta 0), reused 0 (delta 0)
To g...@mygit.test.com:USER01/test01.git
 * [new branch]  develop -> develop
[user01@server01 test01]$
 

>  
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/gitlabhq/cb603cee-94fc-4820-9df0-2eb0559a2344%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Gitlab CE 8.3.2 Update

[T.J. Yang]

There is an issue opened 
 similar with your 
question.

On Thursday, June 23, 2016 at 1:50:49 AM UTC-5, Tatva Soft wrote:
>
>
>
>  I am using gitlab  version 8.3.2 CE and i have enable check version 
> checkbox in my application setting so i can see text "update asap" with red 
> color. you can see attached image for the same.  so i want to know that to 
> do update is compulsory or not? lets say if i am not updating then will 
> this current version will not work in future at least for 1 or 2 years ? 
> because i am am okay with the current version and i don't want to update 
> with newer one at this moment. can you please provide valuable suggestion ?
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/gitlabhq/4a8f02f0-e6e4-4f11-b624-5992713b4aa8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: HA for Gitlab

[T.J. Yang]

I had implemented a few  HA services using pacemaker+drbd on Centos 7.2.
I like to implement the the same for gitlab-ce to have 1st and 2nd VM write 
shared drbd disk/filesystem via network.(See R1)
/var/opt/gitlab, /etc/gitlab and /var/log/gitlab are all reside on drbd 
drive mounted as /pub dir. following are the links pointing to shard drbd 
drive /pub

[root@re02 ~]# ls -ld /etc/gitlab /var/log/gitlab /var/opt/gitlab
lrwxrwxrwx 1 root root 22 Jun 13 12:42 /etc/gitlab -> /pub/gitlab/etc/gitlab
lrwxrwxrwx 1 root root 26 Jun 13 12:30 /var/log/gitlab -> 
/pub/gitlab/var/log/gitlab
lrwxrwxrwx 1 root root 26 Jun 13 12:36 /var/opt/gitlab -> 
/pub/gitlab/var/opt/gitlab
[root@re02 ~]# ls -ld /pub/gitlab/*/*/*
-rw---  1 root root 35792 Jun 12 07:36 /pub/gitlab/etc/gitlab/gitlab.rb
-rw---  1 root root 35904 Jun 10 17:41 /pub/gitlab/etc/gitlab/gitlab.rb~
-rw---  1 root root 35904 Jun 12 06:44 
/pub/gitlab/etc/gitlab/gitlab.rb.orig
-rw---  1 root root  6347 Jun 13 14:06 
/pub/gitlab/etc/gitlab/gitlab-secrets.json
drwxr-xr-x  2 root root  4096 Jun 10 17:25 /pub/gitlab/etc/gitlab/ssl
drwxr-xr-x 12 git  root  4096 Jun 13 12:30 /pub/gitlab/var/log/gitlab
drwxr-xr-x 13 root root  4096 Jun 13 14:06 /pub/gitlab/var/opt/gitlab
[root@re02 ~]#


I shutdown the 1st VM cleanly to relase /pub and failed over /pub to 2nd 
VM. But I can not startup gitlab-ce instance on 2nd VM. Even I tried to run 
"gitlab-ctl reconfigure", it hang at unicorn_sleep.

@@ -1 +1,4 @@
+#!/bin/sh
+echo "Received TERM from runit, sending to process group (-PID)"
+kill -- -$(cat /opt/gitlab/service/unicorn/supervise/pid)
- change mode from '' to '0755'
- change owner from '' to 'root'
- change group from '' to 'root'
  * link[/opt/gitlab/init/unicorn] action create
- create symlink at /opt/gitlab/init/unicorn to 
/opt/gitlab/embedded/bin/sv
  * link[/opt/gitlab/service/unicorn] action create
- create symlink at /opt/gitlab/service/unicorn to 
/opt/gitlab/sv/unicorn
  * ruby_block[supervise_unicorn_sleep] action run



Anyone can give some pointer why reconfigure hang on 2nd VM with data from 
1st VM ?

Currently I plan to do fail-over manually. Once I got more understanding of 
gitlab-ctl and runsvcdir systemd serivice.
I will attempt to write the OCF agent for gitlab-ce service.

R1. 
https://gitlab.com/gitlab-org/gitlab-ce/raw/master/doc/administration/img/high_availability/active-passive-diagram.png


On Tuesday, April 28, 2015 at 9:43:17 PM UTC-5, Kendall Green wrote:
>
> Does anyone have solution for how to manage HA for GitLab CE?
>  
> Here's the challenges, currently with old version GitLab non-omnibus 
> install on mysql 5.1, and needs to be upgraded soon, non-omnibus and setup 
> with high-availability. 
>
> I will probably need to upgrade again, without using omnibus, or 
> postgresql. Are there any documents specific for this?
>
> I attempted this before discovering that I can't use pgsql, I had followed 
> procedures in docs for converting database to pgsql and upgraded with 
> omnibus to latest version. That appeared to work correctly despite LDAP 
> config part and some odd index already exists output for converting to 
> postgresql. The issue is, this embedded redis and postgres doesn't have HA 
> / clustering for gitlab, and I have to use mysql instead of pgsql. 
>
> I think this means that I will need to take my existing old gitlab on 
> mysql innodb, convert to ndb(unsure of) for HA, and attempt a custom setup 
> for both redis cluster and mysql_cluster, and the data on nfs... I'm not 
> sure if there are any database issues with MySQL_Cluster, and GitLab, or if 
> there are any related docs or anyone can reply with best approach at HA 
> with latest release GitLab using MySQL database and redis cluster as it 
> relates to the application.
>
> Thank you!
>
> -Kendall Green
>
>   
>
> On Thursday, October 11, 2012 at 9:54:53 AM UTC-7, Steve Pereira wrote:
>>
>> Does anyone have any experience with configuring Gitlab to be highly 
>> available? I'd like to have 2 Gitlab servers behind something like HAproxy 
>> in order to have a seamless failover in place.
>>
>> If this is something more people are interested in I'd be happy to share 
>> my findings here if I have to set it up from scratch. 
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/gitlabhq/30fab2c3-21e1-4c5b-8dbf-d042fde878af%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.