About LAMurakami GitLab/GitHub Pages

Welcome to the LAMurakami GitLab/GitHub Pages Static Website

Since 2024 this site has been hosted on GitLab Pages. This was done by creating a YAML file specifying a deploy to GitLab Pages. GitLab Pages is similar to GitHub Pages and serves static pages only. GitLab has a different deployment using their Continuous Integration and Delivery (CI/CD) component of Projects. I moved to GitLab because they support IPv6 and IPv4 and GitLab only supports IPv4 except for GitHub Pages.

Since 2020 this site has been hosted on GitHub Pages, a free, static site hosting service for open-source projects on GitHub. GitHub Pages takes HTML, CSS, and JavaScript files straight from a repository on GitHub, optionally runs the files through a build process, and publishes a website. The service is both fast and reliable thanks to the content delivery network. GitHub Pages source repositories have a recommended limit of 1GB, and a soft bandwidth limit of 100GB per month. Recommended and soft mean you may receive a polite email from GitHub Support suggesting strategies for reducing the site's impact on GitHub servers. GitHub or may decline to serve the site but probably not before some emails.

The GitHub Pages service has a very important limitation: It serves static pages only. This means no scripts, no query parameters, no dynamic content generated on the server side, no options for injecting any server-side configuration (e.g., .htaccess). The build process which is triggered after changes have been pushed to the publishing source repository may be throttled if too many updates are made too fast.

The static pages only limitation means no directory browsing among other things. A directory without a static index page returns a 404 File not found error even if it exists and has content within.

../Zz/z20/z2006/2020-06-04 - I built an index
../Zz - I built an index
../Zz/z20 - no static index file
../Zz/z20/z2006 - no static index file

You can however browse the repo tree: https://gitlab.com/LAMurakami/lamurakami.gitlab.io/-/tree/master/Zz

This is a Public site and the publishing source is open-source

A clone of the source can be made in any directory you have write access to with the following:

git clone https://gitlab.com/LAMurakami/lamurakami.gitlab.io.git
cd lamurakami.gitlab.io

If the location you downloaded to is within the DocumentRoot of a site the Static Website copy should work as long as the pages all use relative references as intended. I use a location within a site (currently https://ak20.lam1.us/github) so I can test that the links are relative.

This is a Secure site and will enforce HTTPS protocol

The http://github.lamurakami.com, http://lamurakami.github.io , and https://lamurakami.github.io domains will all redirect to the https://lamurakami.github.io secure domain using the wildcard certificate for GitHub subdomains. In HTTPS, the communication protocol is encrypted using Transport Layer Security (TLS) or, formerly, Secure Sockets Layer (SSL) providing authentication of the website, and protection of the privacy and integrity of the exchanged data while in transit.

Log

Published Page locations: https://lamurakami.gitlab.io/About https://lamurakami.github.io/About
Published Clone Page location: https://ak20.lam1.us/github/About
Sunday, July 28, 2024 - Publish to GitLab Pages as well as GitHub Pages
Saturday, July 9, 2022 - https://lamurakami.github.io will be the website and http://github.lamurakami.com a redirect.
- In 2022 I started moving the GitHub pages to the default lamurakami.github.io namespage instead of separate domains.
- Besides the DNS changes the CNAME file was deleted.
Wednesday, June 3, 2020 - Add an About page with the text from the site main page.
- The main page will be a repository index with a link to the new about page.
- In 2020 when I started investigating GitHub Pages after creating the required lamurakami.github.io repo and making it a GitHub Page I made some of the existing repos GitHub Pages as well. The initial guide I had used had created a page that used Jekyll and the _config.yml to convert the default README.md of a repo into an index.html page. I then used the datasciencecoursera repo and added a /docs directory as the GitHub pages source. This page did not use the Jekyll build process during the publish hook tied to Github seeing a new commit for a repo with GitHub Pages specified. For a third page I used the datasharing repo and created a new gh-pages branch and selected jekyll-theme-cayman from the GitHub web interface. This resulted in a commit with a new _config.yml file that contains theme: jekyll-theme-cayman
Sunday, May 31, 2020 - Many updates to this site and my LAMipedia GitHub Page.
Saturday, May 30, 2020 - Created the repository and this site.
- This is the first of LAM sites that does not use a self generated certificate that is automatically branded as not trusted by most browsers for the secure side of the site.. I initially found that Enforce HTTPS was Not yet available and then saw that a certificate for github.lamurakami.com good for 90 days was generated within minutes. The GitHub Pages documentation topics start with the defaults of generating a site index.html file from the README.md file using GitHub Flavored Markdown which is the default syntax for styling GitHub writing. The page generation is done using a Jekyll theme selected from settings and saved in the Jekyll _config.yml configuration file. I am new to Jekyll and was not particularly happy with any of the 10 or so themes I briefly examined.
- I initially selected one of the Jekyll Themes and used the editor on GitHub to update the README.md Markdown file for this new site.
- I decided this will be a Static Page from a MediaWiki page using the manual process I have been using for years rather than the Jekyll process, Themes I don't particularly like, and the GitHub Flavored Markdown I am less familiar with than html.