Cloudron App Packagers
@robi I do not mean that it is impossible to do. I said that it would not work in this case with the current software : Even if one manages to find a nginx config which would work, Cloudron does not support custom edits of the nginx config, as they would get overwritten all the time. And this would be very custom ^^
@brutalbirdie Do you mean all OWNER TO gitlab;?
So in RegEx OWNER TO.*;$
@girish said in Gitlab - How to restore / migrate a non Cloudron Gitlab:
Now to update the dump, on linux atleast, this is easy using the Gnome archive manager. You can just open the tar file. Inside there is db/database.sql.gz. Open that again. Then in text editor, just replace all the userxxx in the file to be this new useryyyy.
I am not quite sure which userxxx you are referring to which is to be replaced.
A more explicit search string would be really helpful.
@7dowwilkes Honestly, I don't think there is any way to do it with cloudron, as 443 is already taken by HTTPS and there is no way to do both on the same server (well, there are, but they would not work in this case).
However, I think you should look for other ports that your network will allow through, there most probably are some others, like IMAP / SMTP ports, maybe ftp, stuff like that. You most probably would be able to put OpenVPN on these and get it to work.
this is what my Cloudflare DNS Dashboard now looks like.
Yes the MX still reveals the real IP.
This is more like a small inconvenience for DNS scanners / script kiddies.
@girish Awesome! Will test this out!
[1.55.3]
@brutalbirdie I don't have an installation outside Cloudron but I tried a test backup/restore of between Cloudron instances. In the process, I found a bug in the package, so please update to latest package first (1.55.3).
This is for backup for an app installed in Cloudron. If GitLab is outside Cloudron, skip this step and somehow make a backup following https://docs.gitlab.com/ee/raketasks/backup_restore.html#restore-gitlab
Installed GitLab. Creates repos, uploaded ssh keys and made some configuration changes.
In a Web Terminal, I typed:
sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production
This creates a backup .tar file under /app/data/backups. Mine was named 1632462433_2021_09_24_14.2.3_gitlab_backup.tar
Install GitLab on Cloudron. Make sure the GitLab version matches between what you have outside Cloudron with the Cloudron package. The current GitLab version on Cloudron is 14.2.4.
Fix up the db file - This is a slightly awkward step. The dump inside the backup contains a reference to the previous installation's postgresql user. First, make a note of the new postgresql user. You can do this by running env | grep POSTGRESQL_USERNAME in the web temrinal (let's call this useryyyy). Now to update the dump, on linux atleast, this is easy using the Gnome archive manager. You can just open the tar file. Inside there is db/database.sql.gz. Open that again. Then in text editor, just replace all the userxxx in the file to be this new useryyyy. When you save and close the editor, it will ask to update the database.sql.gz. And then when you update the database.sql.gz, it will ask to update the backup .tar file. (there are two updates/saves).
Now upload the .tar file in /app/data/backups of the new installation.
In Web terminal,
sudo -u git -H GITLAB_ASSUME_YES=1 bundle exec rake gitlab:backup:restore RAILS_ENV=production
I got output like:
...
2021-09-24 06:22:36 +0000 -- done
2021-09-24 06:22:36 +0000 -- Restoring uploads ...
2021-09-24 06:22:36 +0000 -- done
2021-09-24 06:22:36 +0000 -- Restoring builds ...
2021-09-24 06:22:36 +0000 -- done
2021-09-24 06:22:36 +0000 -- Restoring artifacts ...
2021-09-24 06:22:36 +0000 -- done
2021-09-24 06:22:36 +0000 -- Restoring pages ...
2021-09-24 06:22:36 +0000 -- done
2021-09-24 06:22:36 +0000 -- Restoring lfs objects ...
2021-09-24 06:22:36 +0000 -- done
This task will now rebuild the authorized_keys file.
You will lose any data stored in the authorized_keys file.
Deleting backups/tmp ... done
Warning: Your gitlab.rb and gitlab-secrets.json files contain sensitive data
and are not included in this backup. You will need to restore these files manually.
Restore task is done.
secrets.yml from old installation into new installation's /app/data/secrets.yml. You might also have to copy over other gitlab.yml settings into /app/data/gitlab.yml.
@neluser I have pushed out update to 4.2.2. But I don't think the redmine version upgrade will fix the gem installation problem. I made some progress today with trying to figure how to get gems to install out of the plugin directory that redmine can also use. I will continue the work tomorrow.
[1.7.2]