💾 Archived View for jacksonchen666.com › posts › 2023-12-01 › 19-29-37 › index.gmi captured on 2024-06-16 at 12:20:00. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2023-12-28)
-=-=-=-=-=-=-
2023-12-01 19:29:37Z (last updated 2023-12-01 19:29:37Z)
While I'm trying to get certificates for reinfo.wiki, I'm going to talk about setting up new domain names for stuff.
Usually, I may put my stuff under a subdomain on jacksonchen666.com, like videos.jacksonchen666.com or status.jacksonchen666.com or files.jacksonchen666.com.
Those kinds of new domains are easy to deal with:
1. Add more nginx configuration
2. Use a subdomain as the `server_name`
And that's it. The server software part is pretty specific and setup varies, so that's not included in the list.
But what about the cases of new different domains? Like reinfo.wiki?
Well, that involves a lot more setup. Here's the case for reinfo.wiki:
0. Get the domain name
1. Setup authoritative nameserver (if not setup already)
2. Add a domain in deSEC.io
3. Setup DNSSEC
4. Setup DNS records
5. Get certificates
6. Setup the software that's gonna run the thing (already done)
7. Setup the Tor Onions
8. Add nginx configuration
9. Do HSTS preloading
10. Update prometheus and blackbox configuration (the uptime checker)
11. Update links in many places (specific for reinfo wiki as it already existed)
12. Add CAA records
Yeah, there's a lot of work involved in a new domain name that isn't just a subdomain.
So yeah that's it I guess. There's not much special about the setup.