hubelbauer.net

This repository hosts my personal website.

To-Do

Extract Location redirect check script to a reusable function

Use hubelbauer.com-redirect.sh as a baseline as it has some extra checks the other versions do not at the moment.

Add a workflow to push into this repo once a month to keep workflows alive

GitHub now disables workflows after 60 days of repository inactivity.

Collect workflow runs data using GitHub API and display uptime charts

Sometimes some of the redirects act out, I would like to see how often so let's add some charts.

Dump extra information in a case of a workflow failure

When checking for example a DNS record or an HTTP header, in case of failure, dump the whole DNS recordset or the whole HTTP response including all headers and the body to aid debugging.

Add pipelines that check DNS records of the redirect domains

While I'm at it, why not also check the DNS records of the redirect domains to make sure they don't contain records I don't expect to see. I will likely find records to remove while setting this up. What should be left is basically just Wedos DNS servers and Wedos email records. I should do this for hubelbauer.net, too, but there the situation will be a bit more complex with the Fastmail email setup and so on.

Reuse the DNS and redirect checking pipelines for my other domains elsewhere

For rhaeo.net, rhaeo.com, rhaeo.cz, set up the pipelines in its respective repository.

For musicblackholes.com, set up the pipeline in its respective repository. Also look into extra stuff like proper email setup and uptime checks.

For onewheelprague.cz and other domains I have not discovered yet (there are some in CloudFlare, maybe also in Namecheap and possibly even GoDaddy?), set up a separate repository for checking these away from this repository.

Add tomashubelbauer.today

Forgot about this one! Need to decide whether it should be a different site or a redirect.

Add tom.menu and create a GitHub Pages with optional HTTPS as a link tree

This is is the only domain I have in Namecheap it seems. HTTPS optional so I can do curl tom.menu/x | sh without having to specify https:// and -L.

Add a workflow to check the landing page returns a 200

This will reveal any errors in the GitHub Pages setup.