Contents
In 2015 I created the GitHub account as a "The Data Scientist's Toolbox Task" and it became my default remote for repos that were to be made public. In 2023 when I started investigating the transition to IPv6 to avoid paying for a public IPv4 address I found that GitHub does not support IPv6. Dealing with it became one of many IPv6 only workarounds I developed. In 2024 I created the GitLab account after seeing many complaining about the GitHub lack of IPv6 support say that moving to GitLab is the answer.
One of the main advantages of GitHub public repos was the ability to link to files and even changes in documentation. I now have a lot of links to GitHub in my documentation. New links to source will be to GitLab but I may never get around to fixing all the links to GitHub. It is possible GitHub will remedy the IPv6 deficiencies and will be as good as GitLab for me. It is not too much trouble for me to update both remotes when making changes which is actually three since I also have a private remote.
GitHub Pages is deployed to servers that support both IPv4 and IPv6 but should always link to the copy of source on GitLab or the links will be broken for IPv6 only users.
I maintain a copy of all the repositories that are publicly available on GitLab/GitHub in a private repository store that is a component of a LAM Alaska clone. This remote also has repositories that will not be made public including remote copies of the etckeeper repository for all my machines and the lam repo that has the code for the secure side of LAM Alaska. I support git@server and https:// access to gitweb but only for an authenticated user.
| SSH URLS for git remotes | |||
|---|---|---|---|
| Remote | SSH URL | Published site | Public https: source URL |
| aws | git@aws:lamurakami.github.io | Private repo store | |
| github | git@github.com:LAMurakami/lamurakami.github.io | LAMurakami GitHub Pages | https://github.com/LAMurakami/lamurakami.github.io |
| gitlab | git@gitlab.com:LAMurakami/lamurakami.gitlab.io | LAMurakami GitLab Pages | https://gitlab.com/LAMurakami/lamurakami.gitlab.io |
A single master branch of this repo is used to publish to both GitLab Pages and GitHub pages. The update of the published pages is triggered when a new commit of the master branch of the repo is pushed to the respective remote. Both GitLab and GitHub require the repo name to be in a specific format for publication as my main page on the two platforms.
I initially copied 9 repositories used for a LAM Alaska Clone on AWS then the gci and qemu repos used for a LAM Alaska LAN clone. I then added the lamurakami.gitlab.io which is lamurakami.github.io on GitHub and is the source of my GitHub Pages and configured it to be the source of my GitLab Pages as well.
After publishing some GitHub Pages I decided that I should upload more repos just for the value for documentation.
This page
was last updated
Wednesday, January 8, 2025 @ 1:54:55 AM (Alaska Time)