Support installing packages from other sources

A number of organisations do not have direct access to packagecloud from a production environment.

Can we make this an option in the cookbook going forward?

You can download package from https://packages.gitlab.com/gitlab/gitlab-ce and install it manually.

That doesn't really work for me sadly. Whilst the omnibus installation is just a package install, we control node configuration from the Chef server.

I expect many other organisations will be in the same boat.

I think we're in a similar boat, with VERY rigid internal and external firewalls. Access to gitlab for RPMs will be blocked by default, but we're hoping to allow for a spacewalk/satellite box to have access to cache packages.

Changing the URL in the attributes should do the trick for us handily. Will that work for you too, @DanW85 ?

Update: @DanW85 , we went with a custom cookbook external to cookbook-omnibus-gitlab, which pre-installs the gitlab-ce from a copy in files/default, and then includes the omnibus-gitlab cookbook. Yes, it's a ridiculous 400Mb cookbook, but when spacewalk lights up we'll go behind and trim it.

It seems to go well, (but we're still gnashing our teeth on the "please use the web form to go reset the password by hand unless someone jumped onto the box and stole it first" race issue. I sinCEREly hope pros didn't write it like that without a fix, lest the predicates find a challenge. And hey, if you're cheffing gitlab-ce too, show me where I can set the ENV and have that pre-populated ... if that still works!)

Update: and here's the answer for seeding the admin password effectively.

https://docs.gitlab.com/omnibus/settings/database.html#seed-the-database-fresh-installs-only

It's an easier race condition when you're only competing with locals.