eupolicy.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
This Mastodon server is a friendly and respectful discussion space for people working in areas related to EU policy. When you request to create an account, please tell us something about you.

Server stats:

211
active users

#namecheap

0 posts0 participants0 posts today

I'm in a situation where an organization has a #ReadTheDocs website registered as `<project>.io` (via #NameCheap). Note that no one in this organization are experts or even practitioners of web publishing. People are realizing that the documentation site is not the best landing page and want to do two things:

1. move the documentation site to `docs.<project>.io`
2. set `<project>.io` to host the landing page built on #GitHub with links out to `<project>.io`

The question is: how the heck does one go about doing this without borking everything? It's clear that external links to the documentation would need to change, but in the meantime, I can see the following:

1. register `docs.<project>.io` and add that to the domains in #ReadTheDocs
2. set `<project>.io` as the CNAME for the GitHub site
3. add JavaScript to the 404 page that detects if the link is attempting to point to the documentation site and provide the correct redirect.

Is there anything else that I'm missing? #Web #DNS

So I've just managed to move all my manual domain configuration in #namecheap into Terraform / OpenTofu.

Needed to write an exporter script, which requires the Namecheap API be enabled (Settings -> Tools -> API)

And then here's the tool I used to export to Terraform:

gist.github.com/ThisIsMissEm/9

I'm totally not fully maintaining this, but if it helps someone, fantastic.

GistIf you're wanting to export data from Namecheap into Terraform / OpenTofu, here's the code I used:If you're wanting to export data from Namecheap into Terraform / OpenTofu, here's the code I used: - .env.example