PiBox

Gogs comes up very easily (see src/web/gogs/notes.txt). The main problem seems to be how to import existing repositories. You can migrate them manually via the Web UI, but with lots of repos that can get rather tedious.

Also, there is the issue of whether this would be a git mirror or not.

Other import resources

• https://phoenixnap.com/kb/how-to-create-mariadb-user-grant-privileges
• https://www.techrepublic.com/article/how-to-host-your-own-local-git-repository-with-gogs/
• https://www.howtogeek.com/855298/gogs-is-the-easiest-way-to-run-a-local-git-server-how-to-set-it-up/
• https://xo.tc/setting-up-gogs-on-debian-jessie-with-apache2-and-postgresql.html

Migration API: https://github.com/gogs/docs-api/tree/master/Repositories#migrate
Gitlab to gogs migration script: https://gist.github.com/gregdel/870d58c80b80172445dc93294531d88c
General migration script: https://gist.github.com/senz/bd6f4754300f335bf051ddee1d93af5d

Git Mirror vs Clone: https://sourcelevel.io/blog/how-to-properly-mirror-a-git-repository

Updated migration script works fine using tokens (not passwords). I found that I should create "orgs" in place of GitLab groups when migrating, but I need to create the groups manually. Alternatively, I could check the GOGS API to see if I can add the group creation with the script.

One other thing I need to check the API for is Mirroring. I want to mirror my repos for now, but convert to regular repositories if GitLab goes wonky on me.

Finally, I want to add a -f option to the script that will read the values that would otherwise be set on the command line. I want to be able to create a single file of repos to migrate so it can be done in a loop.

The script is working to create orgs (re: groups) and migrate repos using a -f masterfile where each line is a config file for a repo to migrate. This will allow me to create a complete list of my repos to migrate as well as lists of 3rd party repositories to mirror.

However, I need to find the GitLab API that retrieves the repos description so it can be added to the GOGS repo migration.

Note that all migrations are mirrors at this point. That's fine for now.

Update:
Try get single project API to get the description. Note that I need the project ID or name (url-encoded) in this API. I have 10 groups (not all active) on GitLab and I'll need to mirror them all on GOGS which means finding the project ID for all projects in all groups. It also means adding a GITLAB_PROJECT_ID variable to each config file. But hey, I only have to do this once, really.

Mirroring 3rd party repositories will be manual. In some cases, like GTK2, I may have to recreate a repository from source.

Update:
Or maybe not

Fixed the description retrieval. The script now creates the repos as mirrors with descriptions.

All that's needed now is to create the set of config files for all my repos.

Then create a masterfile for all the 3rd party repos I want to mirror.

Once those are created and tested locally, I can setup Gogs on the colo server and run the script.

Then, finally, I can start creating new repos of all my old software instead of just dumping it as compressed archives in the archives tree.

The configs on the muse site have been updated to use the graphics-muse site instead of the local host I used for testing.
All that's left is to run the migration script with the masterfiles and updated configs.

At that point all my repos from gitlab will be mirrored on my gogs site and I can start (outside of this issue) to migrate my old source to the Gogs system and start to mirror projects I think are in danger of disappearing.

All non-empty repositories have been migrated as mirrors.
The Gogs interface is now linked from the Muse web site. It will be added to PiboxProject tonight.
Closing issue.

Gogs was hacked, possibly due to not properly configuring admin access. The hackers did a DoS by filling my disk with projects. I had to remove them manually from the server. I disabled Gogs.

I found I could mirror GitHub projects on GitHub. I've done that with the Raspberry Pi repos.

The next option I found is to fork projects into the public GitLab service under my account. I've done that with Raspberry Pi Linux, Userland and omxplayer. Others will come later.

The next thing I found is that I can run a private docker instance of GitLab in a container. The setup suggests using docker-compose, but a simpler startup uses docker engine. This runs out-of-the-box and I can map host ports to container ports to hide it a bit. This allows me to, for example on the test instance on galileo, access the UI as

http://galileo.gfxmuse.org:1880

or

https://galileo.gfxmuse.org:1443

The container version could also be used in-home, so I could have a public instance on muse and a private one at home that mirrors repos.

I'm experimenting with the private GitLab instance in docker to make sure I use it correctly. To get a shell in the docker container

sudo docker exec -it gitlab /bin/bash

There is a configuration file under /home/gitlab/gitlab.rb where I can setup use of muse's smtp. After making config changes I run

gitlab-ctl reconfigure

to update the running instance. To run rails commands (such as testing email)

gitlab-rails console
Notify.test_email('destination_email@address.com', 'Message Subject', 'Message Body').deliver_now

I can stop the running instance with

sudo docker stop gitlab
sudo docker rm gitlab

and restart it with a script I wrote in ${HOME}/bin called gitlab.sh . To get the initial password

sudo docker exec -it gitlab grep 'Password:' /etc/gitlab/initial_root_password

When the time comes, I can upgrade the whole thing fairly easily.

I can also sign up for a newsletter for security updates.

Changing the admin (and my user, which is also an admin) password is easy and it works fine in the docker image.

These are done but X.org and matchbox both have multiple repositories that could be mirrored.

I'll close this for now. If I need to do more, I'll add new issues.