LAMurakami GitLab/GitHub Pages

Welcome to the LAMurakami GitLab/GitHub Pages Static Website

https://gitlab.com/LAMurakami GitLab user for all my Repos - https://gitlab.com/aws-lam - My GitLab Pages Group
- https://lamurakami.gitlab.io - My GitLab Pages website
  - Published from master branch of https://gitlab.com/LAMurakami/lamurakami.gitlab.io Project
  - Pipeline defined by the .gitlab-ci.yml YAML file to deploy plain html to GitLab Pages
https://github.com/LAMurakami GitHub user for all my Repos
- https://lamurakami.github.io - My GitHub Pages website with Enforce HTTPS specified
  - Published from master branch of https://github.com/LAMurakami/lamurakami.github.io repo
https://lamurakami.github.io/blog - LAMurakami Blog and Websites collection on GitHub Pages
- Published from gh-pages branch of the https://github.com/LAMurakami/blog repo
About- About LAMurakami GitLab/GitHub Pages

Why GitLab and GitHub?

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. I will move to links on GitLab instead but may never change all the links I previously created. 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.

New links to source will be to GitLab but I may never get around to fixing all the links to GitHub. 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.

LAM Alaska git repository store

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.

GitLab has a public project for repos that have recent activity

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.

LAMurakami / lamurakami.gitlab.io aws-lam / aws no-ssl sites arsc cabo z blinkenshell olnes larryforalaska gci qemu

Repos for LAM AWS Linux Apache MariaDB in the cloud

After publishing some GitHub Pages I decided that I should upload more repos just for the value for documentation.

aws#readme Linux Apache MariaDB in the cloud
no-ssl#readme Default unsecure site <http://> configuration.
arsc#readme Lawrence A. Murakami at ARSC
sites#readme LAM Sites in the cloud and at home in Alaska.
z#readme A place to publish simple pages
cabo#readme Cabo San Lucas, Baja California Sur, Mexico.
ubuntu-etc/#readme Ubuntu Server 20.04 configuration changes for LAM AWS VPC EC2 instances

More Repos with recent activity (since I retired)

qemu#readme QEMU (Quick Emulator) cloud-init repository
blinkenshell#readme http://lam.blinkenshell.org

Some repos from 2015 when I created my GitHub account for a course

https://lamurakami.github.io/datasciencecoursera
- Published from /docs directory of master branch of datasciencecoursera repo with Enforce HTTPS
https://lamurakami.github.io/datasharing
- Published from gh-pages branch of datasharing repo with Enforce HTTPS
  - The the gh-pages branch has the _config.yml file that specifies the jekyll-theme-cayman theme.
- The index.html page is generated from the README.md file in GitHub Flavored Markdown the default syntax for styling GitHub writing.
https://lamurakami.github.io/rhel-skel
- Published from /docs directory of master branch with Enforce HTTPS