Open stephenlauck opened 10 years ago
is this cookbook goin tot adopt the recomended method for installation given by the docs? https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/install/installation.md
Note they give us a "strongly" not only recommend. So, that conversion would make sense, right?
Since an installation from source is a lot of work and error prone we strongly recommend the fast and reliable Omnibus package installation (deb/rpm).
I don't know whether the mentioned refactor is still in progress due to the age of this issue being open - but for anyone interested, I wrote a from scratch re-implementation cookbook (https://github.com/dnadesign/cookbook-gitlab-omnibus) that uses the provided ombinus package installation, and follows the chef-server cookbook pattern (which is also an omnibus install) - to provide resources that utilize the gitlab-ctl
command the package provides etc. I no longer work for that organisation (or run gitlab actually) - but it might be useful prior art if anyone's considering such a refactor on this cookbook. IMO installing via the package makes keeping the cookbook up to date with the latest gitlab versions a lot easier, because most of the hard config is done inside the omnibus'd package, and you only need one config file + gitlab-ctl reconfigure
for the entire gitlab stack.
I would like to use the omnbus gitlab install to simplify the cookbook. I haven't had the time to work on that. I will probably hack on it over holiday vacation when I have ample free time.
+1
I am working on a refactor that is cross platform and uses the omnibus install. Gitlab provides a cookbook for this, but I think it could be more cross platform and not depend on data bags.
Here is the gitlab one: https://gitlab.com/gitlab-org/cookbook-omnibus-gitlab