@gitlab-greg So I solved the issue of deleting and renaming projects. I posted the Issue here on GitLab.com and got some very quick feedback. All I had to do was follow the steps under When the secrets file is lost and now I get no more errors when deleting or renaming projects.
There is still the major problem of importing the project: I tried again last night to import through the GUI, and not everything was pulled:
- Old/Live GitLab: 20 GB ( 403.1 MB repository, 0 Bytes build artifacts, 19.6 GB LFS )
- New GitLab: 19 GB ( 0 Bytes repository, 0 Bytes build artifacts, 19 GB LFS )
I also tried importing through API in Terminal, but I don’t think I’m getting the file= part correct … not sure what I’m supposed to put to be honest:
root@gitlab:~# curl --request POST --header "PRIVATE-TOKEN: <my_api_sudo_access_token>" --form "path=company-name" --form "file=@gitlab.domainname.cpm/company-name/Project.git" https://gitlab.domainname.com/api/v4/projects/import
Warning: setting file gitlab.domainname.com/company-name/Project.git
Warning: failed!
curl: (26) read function returned funny value
I realize that even if I still get the full contents of the project, it may not include the current Issues, User Accounts and the Slack Integration I have set with the Live GitLab. A full backup of the Live GitLab and restore to the New GitLab is probably the best solution … but I want to know:
- Is there a way to backup and restore the Live GitLab in the New GitLab environment without the restore touching the
/etc/gitlab/gitlab.rb? - Is there a way to backup and restore the Live GitLab in the New GitLab environment without the restore touching the CI/CD variables and Runner registration tokens that I just fixed?