[Gitlab] Current Status of the port

[Torsten Zuehlsdorff]

Hello,

>>>>>>> I've created a basic working configuration for default.
>>>>>>> You just should change the "host" in config/gitlab.yml,
>>>>>>> if you want to use something other than "localhost". The
>>>>>>> rest should work. But please test carefully, i've done
>>>>>>> many changes in the last months.
>>>>
>>>> I built the packages and installed them in a jail, then
>>>> followed the guide. Setting up redis, the database, config,
>>>> precompiling assets, etc. went fine. When I tried to startup
>>>> gitlab, I get this in the unicorn log:
>>>>
>>>> I, [2015-07-31T19:00:43.855792 #80415]  INFO -- : Refreshing
>>>> Gem list
>>>> [.. ]
>>>>
>>>
>>> After commenting out line 5 of:
>>>
>>> /usr/local/www/gitlab/app/controllers/import/bitbucket_controller.rb
>>>/usr/local/www/gitlab/app/controllers/import/gitlab_controller.rb
>>>
>>> I have gitlab up and running. This may be related to some local
>>> patches I have to ruby and gem. Anyway, I'll keep testing it. So
>>> far so good!
>>
>> After some testing and research i tend to remove the options and
>> enable the providers by default.
>>
>> The documentation advises the user to enable the OAuth(2) methods
>> by simply configure them. Therefore they should already be
>> installed.
>>
>> At the moment you can choose between MySQL and PostgreSQL, but the
>> project highly advises against MySQL.
>>
>> In conclusion i would remove all options, make the OAuth providers
>> installed by default and remove the MySQL completely.
>
> Assuming BitBucket OAuth is installed, can people login to my
> (hypothetical) GitLab installation without further configuration or
> explicitly enabling it from my side?

You need explicitly enabling it in config/gitlab.yml.

Gitlab needs the Gem installed, but for further use you need explicit 
configuration. Its commented out by default.

>>
>> Is somebody against this approach? Otherwise i will try to get
>> this ready today/tomorrow :)
>
> /holds hand up up/
>
>
> Personally, I like PostgreSQL much better than MySQL, but for the
> port, I don't think we should force users to give up on their
> MySQL/MariaDB installations just because. There are a lot of
> FreeBSD+MySQL/MariaDB users out there.

Thats the case why i originally added to option. But i changed my mind 
after reading this again and again:

https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/install/database_mysql.md

This implies that the usage of MySQL will come with various problems, 
which won't be fixed.

> Could you just make postgres the default one, so that the packages
> are built with it and everything else needs extra work for those who
> desparately want it?

Yes. I removed this an hour ago for further tests. But of cause i can 
bring it back. Do you hold your hands still up? Then i will bring it back.

Greetings,
Torsten