jboxberger / synology-gitlab-ce Goto Github PK

Despite most stuff working fine, there is one issue, I couldn't resolve:

• the external url of the gitlab (e.g., one it provides the cloning URL) is: synology-gitlab-ce (which is not even a correct url)
• so I attempted to modify this:

1. ssh to NAS and bash into the docker container (as per above)
2. edit the external URL as per https://docs.gitlab.com/omnibus/settings/configuration.html
3. sudo docker exec -t "synology-gitlab-ce" bash -c "gitlab-ctl reconfigure"
4. sudo docker exec -t "synology-gitlab-ce" bash -c "gitlab-ctl restart"

Unfortunately, this didn't work: even though, there were no obvious error messages (there was a huge amount of output to "reconfigure"), when everything was finished, even after several minutes no access was possible, i.e., Gitlab was no longer available at the URL, it was available previously as this was the URL used for reconfiguration.
(http://xyz.synology.me:30080/

However, I could successfully revert the process, luckily.

I followed all the instructions, and no matter what I do, the furthest I can get is Docker telling me the container failed to start because /assets/wrapper does not exist.

What am I missing, and how do I get this to work?

I'm looking at this and not really getting how to use it.

I'm looking to install GitLab on a new diskstation. I had been using the old Synology package on a 918+ but the lack of attention from Synology is a shame.

The synology-gitlab-ce-15.1.2-dsm7-advanced.spk. What do I do with this file? It's not mentioned in your instructions at all. Is this a package that needs installing on the NAS?

Your commands like 'cd /var/packages/synology-gitlab-ce ... ' Are these commands being run on the Synology?

Have to admit this is all a little confusing.

Clearly the underlying gitlab-ce is covered by their license.

Please write something to describe the license you apply to your changes / adaptations for Synology use. Doing so will provide users with clarity and peace of mind.

I suspect you are pretty flexible about license terms and this is not a big limitation. I suspect the gitlab or synology folk would happy to help you figure out what makes sense if that kind of help is needed.

The wizard says that one needs to run the ssh cmd after the installation completes.

On its last page, the wizard has a tick box to directly start the package afterwards. I guess this has no effect but clarification would be great

Do you plane to support DSM7.1?
The DSM7.1's docker is change name to "container manager" so I cannot install Synology-girl lab-ce anymore.

i'm trying for days to update an old gitlab installation, so i can switch to this repo and upgrade to dsm7. For this I'm trying to arrive at version 12.10.6, the lowest version available here.

Unfortunately updating the official synology package to 12.10.6 doesn't work, as it requires a postresql update from 10 to 11 and the bionic release of postresql has been moved to an archive, and even if i change this in the sources.list file the upgrade will fail, as it will download a new image and create a new container reversing any changes.

I successfully upgraded up until 12.4.2 using the predecessor of this package from @jboxberger (non ce version), 12.9 i can run, see projects, commits, etc. but it won't load actual blob data. Upgrade to 12.10.6 fails.

so i tried to build this repo for 12.0.3 or 12.4.2, which installs fine, but the container stops after a few minutes

i have also tried installing 12.10.6 from this repo and downgrade to 12.4.2 or 12.0.3, same errors....

It's not a huge gitlab server, I am ready to export groups and projects and import in another instance, but for this i would have to come as close as 2 minor versions to 12.10.6, which i simply can't manage to do.

i don't know much about any of this, any help would be greatly appreciated!

The latest update on DSM 6.0 for gitlab is 13.12.2 but there is no such release in here.
Therefore no migration path possible as described.
Is it possible to create a release 13.12.2 for the one who like to migrate to your synlogogy-gitlab-ce before upgrading the the DSM to 7.x like me.

I have successfully migrated/updated from a very old synology gitlab instance to this gitlab-ce, all on dsm6. I'm still only at 13.1.11, but slowly making my way up.
I wonder:

• how do I switch to dsm7? anything I have to do to my installed gitlab-ce?
• the upgrade path tool does not let me select your latest release exactly, only 16.2.9 or 16.3.7 - do I need to arrive at one of your releases here, or can I just upgrade to the latest one myself (atm 17.1.0)?

Thank you

First of all: thanks a lot for creating this package. This is really cool!

Being not a typical user of docker on Synology or Gitlab, I managed with a bit of experimentation to set it up successfully. Some issues prompted me to redo the stuff, even though reinstallation was not really necessary (this might help in the readme:

• the time until things are stable (and a connection is possible may take several minutes after the installation is complete. During this no connection is possible or a error message is shown.
• The current package gives 15.1.2, but one can successfully upgrade to: 15.11.6 and then to 16.0.1 (the step through 15.11.6 is recommended and it is necessary to cross-check that migrations in the admin are successful (may require to restart failed migrations).
• a direct import from the NAS git server does not seem to possible (highly annoying). As this only supports ssh and gitlab only supports git, http, and https protocols. The correct way is then to locally create a cloned repo and then manipulate the origins and push. (actually I am not sure, why it works so easily without any security questions, but it does.)

If there is interest, I can also create more detailed descriptions and provide a pull request for the wiki or the readme of this project (right now, I have this only as local notes)

It is not clear to me:
Is it required to build on a Synology NAS or can we build on any Linux system?
Could you clarify this in the readme?