-
@paul-toone Can you tell us a bit more about your uses for gitlab-ee ? Essentially, if it's related to k8s deployment and things like that, it will be quite difficult to make it work in a Cloudron package.
-
@girish Actually, we were just being forward thinking so we'd have EE if we decided to purchase a license, but we never found we needed the features.
I'm currently moving our data to a new server, downgrading to CE and then we will try to upload our data to your container. I'm hoping we don't have any issues dumping an omnibus installation and importing it to your source install.
I assume, we'd really only need to replace the secrets file and configure the gitlab yml file to match the .rb file we have and try to upload the data.
Does this sound correct?
-
@paul-toone I haven't migrated an install from omnibus before, feel free to reach out here as you hit any issues. Your plan sounds about right:
- First, when you install GitLab on Cloudron, make sure the version of GitLab you have and the one installed on Cloudron matches. The best way to find the correct package version to install is https://git.cloudron.io/cloudron/gitlab-app/-/blob/master/CHANGELOG .
- Then, if you click on GitLab app in App Store in the Cloudron dashboard, you can change the package version in the URL bar.
- Then, import postgres - https://docs.cloudron.io/guides/import-postgresql/
- Then, copy over the repositories and secrets file. That should be it, I think.
Godspeed!
-
@paul-toone a json file is actually a valid yml file, so I'd try to just put it there, and hope for the best
-
My attempts failed, unfortunately. However, I am happy to use gitlab's export groups and projects and rebuild our new gitlab server that way. We are fine with this process but cloudron seems to be great for starting new services from a fresh state or if you're transferring existing projects with the same setup (using the same database, for example) I have some questions regarding that but I'll open a new thread on that. Thank you all for your suggestions.
-
@paul-toone said in gitlab-ee question:
I have some questions regarding that but I'll open a new thread on that
Yes, ask away. We are happy to put in tools which will help migration as well. I know it's complicated especially if db version/type is different etc. But I think this is complicated in general even without Cloudron (of course, you probably even attempt to change the db type since you are forced to by the cloudron package
). -
@girish You are correct. It would be difficult no matter what. Moving from omnibus to source is a difficult task. It pretty much boiled down to the secrets file not being converted correctly. The other issue was uploading a tar.gz backup to the container. I waited +2hours to upload the file and at 99% uploaded it just said the the upload failed with no other information given on why it failed. My upload speed is 50 mb/s but I know this is more on DO side, but I'm still puzzled as to why the upload failed.
Either way, we're headed in the right direction and I'm excited with the possibilities.
-
Hello, I apologize for the sudden revival of this topic, but I am in search of similar information.
At the moment, I am advocating within my company for the adoption of Cloudron to enhance our software maintenance efficiency.
(Our infrastructure is not extensive enough to necessitate a dedicated full-time DevOps, making Cloudron an ideal choice for us.)Currently, our use of GitLab-EE is hindering the shift to a "Cloudron system platform."
I am eager to find out if there are any plans to introduce this feature in '2024/25'?
For example, is there a possibility of selecting between the CE and EE versions of GitLab from a dropdown menu during the installation process?Thank you for taking the time to read this, and I anticipate your forthcoming response.
-
@AriusII No plans for next 3 months atleast (but that's as far as our planning goes). But given EE is selfhosted, it's not outside our scope.
