Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GitLab - consider moving to a "omnibus" install?! (currently source) #1287

Closed
JedMeister opened this issue Jan 3, 2019 · 2 comments

Comments

Projects
None yet
1 participant
@JedMeister
Copy link
Member

commented Jan 3, 2019

As per the subject, we are considering migrating our GitLab install from a source install to an omnibus install.

We envision that this will make maintenance easier; both for us and for end users.

The main potential issue is that our current source install uses MySQL as the backend DB. The Omnibus install supports only PostgreSQL DB backend. So we'd need to ensure that a MySQL based install can be migrated to a PostgreSQL one. As noted in a forum comment GitLab does support export/import, so that may be a potential workaround?

Extending on from that, perhaps it would be useful to see if that functionality can be leveraged from the commandline? If so, perhaps we should look to leverage that within TKLBAM rather than the current method (of saving files and DB)?

@JedMeister JedMeister changed the title GitLab - consider moving to a "omnibus" install (currently source) GitLab - consider moving to a "omnibus" install?! (currently source) Jan 3, 2019

@JedMeister

This comment has been minimized.

Copy link
Member Author

commented Jan 25, 2019

This project is currently in progress. Ongoing discussion has now moved here. Anyone interested in being involved in testing and development, please feel free to join us.

@JedMeister JedMeister added this to the 15.2 milestone Jan 25, 2019

@JedMeister

This comment has been minimized.

Copy link
Member Author

commented Jun 23, 2019

Closing this now as we've moved to an Omnibus install of GitLab. Please note that the current release (v15.3) still has a "500 error" as noted in #1315

@JedMeister JedMeister closed this Jun 23, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.