![]() # The tools/fix_synology_gitlab_backup does that for you. Simply replace the "gitlab_user" with "gitlab". ![]() Sudo docker exec -it synology_gitlab bash -c "sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production CRON=1 " # The synology-gitlab psql user differs from the synology-gitlab-ce so we need to # modify the database dump. Sudo docker exec -w "/home/git/gitlab/config " -it synology_gitlab bash For now, you can look up needed configuration and transfer it # manually to your new synology-gitlab-ce instance # backup config # not found a automated way yet # here is the config located but its structure differs from the omnibus package, need # review and testing. Its is basically a backup from synology-gitlab package and restore to Migration can only be done within the same GitLab version. Sudo docker exec -it " " gitlab-rake gitlab:check SANITIZE=true Migration from synology-gitlab package # restore, please omit the "_gitlab_backup.tar" from the backup archive name Sudo docker exec -it " " gitlab-ctl status Sudo docker exec -it " " gitlab-ctl stop sidekiq Sudo docker exec -it " " gitlab-ctl stop puma # restore gitlab configuration # unzip your configuration backup to the config folder overwriting existing files # config folder: /docker//config # after that you can continue with the data restore # restore gitlab data # copy your data backup to the data/backups folder # /docker//data/backups This can be done on any linux and should also work on WSL.Įxcept "jq" there are no special packages/binaries required. GitLab files (data, config) remains on package uninstallĬlone this repository and execute the build.sh shell script within your terminalĪpplication. Keeps container settings (ports, volumes, links) on updates Multiple Instances Overview Advanced vs Classic FeatureĪccess to container environment variables You can test your upgrades and migrations without any risk and downtime. The ssh installer/updater gives you also the ability to run multiple gitlab container instances withĭifferent container/versions and different data shares. This way all your configuration remains the same and you can downgrade and upgrade as you like. ![]() Settings and an update simply exports you current container configuration and imports it again with a modified GitLab image version. This is a more flexible variant because this way you get the full access to the container Runs exactly with the same privileges and setup as the classic non-root approach but you need to execute the installerĪs root to get the setup done. This approach bypass the root privileges limitation of the DSM by running the setup over ssh. ![]() WARNING: All gitlab data will be deleted on uninstall! Backup berfore uninstalling! Upgrade to Advanced is possible, but be careful and backup, backup, backup! During uninstallation of this package all data will be deleted by DSM. However the settings can be changed but only by uninstallingĪnd reinstalling the package again. This is because of the DSM no root privilege policy. But this comes with a tradeoff, container configuration (ports,volumes,etc.) after the installation is not Very simplistic package, installation and basic configuration over DSM, no ssh or root privileges You can download the SPK file in the Releases section. If you need GitLab Support you might get it here. ![]() Please note that I can not give you support for GitLab itself, this project covers only the Synology installation/update routines. The goal of this project is to lower the entry barrier for new GitLab users and give experienced users a little comfort in maintaining their GitLab installation.Įverything this package does, can be also done manually over the Synology Docker NAS Application. This is a docker based GitLab CE package for Synology NAS server using the original gitlab/gitlab-ce image from. ![]()
0 Comments
Leave a Reply. |