replaced links to this website with natconf.dev

src/routes/blog/2026/0317.md

@@ -46,7 +46,7 @@ services:
       PGRST_DB_URI: 'postgres://authenticator:password@database:5432/postgres'
       PGRST_DB_SCHEMAS: 'api'
       PGRST_DB_ANON_ROLE: 'web_anon'
-      PGRST_SERVER_CORS_ALLOWED_ORIGINS: "https://app.denizk0461.dev"
+      PGRST_SERVER_CORS_ALLOWED_ORIGINS: "https://app.natconf.dev"
     depends_on:
       - database
   database:
@@ -78,7 +78,7 @@ Keep in mind that you will not need to open up any of these ports on your firewa
 
 #### Nginx
 
-I'm using Nginx as a reverse proxy here. What does this mean? It means that we can send a human-readable URL to Nginx, such as this: `https://files.denizk0461.dev`, and Nginx will *internally* route us to the place the service is actually running on: `http://localhost:3923`. This has several advantages: as the end user, we won't need to remember the IP address or the port of the services we connect to. As the server administrator, we will only need to expose a minimal number of ports. In this example, port 3923 is actually closed off from the public, meaning that bypassing Nginx and connecting to the service directly, e.g. by typing `https://denizk0461.dev:3923`, is impossible. The only open port is 443, which is a standard port for websites served over encrypted HTTPS. Your browser will always try to connect to a website starting with `https://` on port 443, unless you specify another port. Port 80 is actually also open on my server, as it accepts requests through the unsafe `http://`, but it only redirects to `https://` on 443.
+I'm using Nginx as a reverse proxy here. What does this mean? It means that we can send a human-readable URL to Nginx, such as this: `https://files.natconf.dev`, and Nginx will *internally* route us to the place the service is actually running on: `http://localhost:3923`. This has several advantages: as the end user, we won't need to remember the IP address or the port of the services we connect to. As the server administrator, we will only need to expose a minimal number of ports. In this example, port 3923 is actually closed off from the public, meaning that bypassing Nginx and connecting to the service directly, e.g. by typing `https://natconf.dev:3923`, is impossible. The only open port is 443, which is a standard port for websites served over encrypted HTTPS. Your browser will always try to connect to a website starting with `https://` on port 443, unless you specify another port. Port 80 is actually also open on my server, as it accepts requests through the unsafe `http://`, but it only redirects to `https://` on 443.
 
 I configured Nginx to run both the SvelteKit app as well as the PostgREST backend from the same subdomain. You don't *need* to do this, and I *think* it should even work if you put, for example, the database on a different subdomain, but I can't guarantee it.
 
@@ -86,7 +86,7 @@ I configured Nginx to run both the SvelteKit app as well as the PostgREST backen
 <pre class="code-block">
 server &#123;
     listen 443;
-    server_name app.denizk0461.dev;
+    server_name app.natconf.dev;
 
     location / &#123;
         proxy_pass http://localhost:3000;
@@ -100,12 +100,12 @@ server &#123;
 
 This `server` block serves two functions:
 
-- it serves our SvelteKit app, which by default runs on port 3000, from the root directory of the subdomain (e.g. `https://app.denizk0461.dev`), and
-- it serves the table `customers` from our PostgreSQL database, which is accessible through PostgREST on port 3100, on the subpage `/customers` (`https://app.denizk0461.dev/customers`).
+- it serves our SvelteKit app, which by default runs on port 3000, from the root directory of the subdomain (e.g. `https://app.natconf.dev`), and
+- it serves the table `customers` from our PostgreSQL database, which is accessible through PostgREST on port 3100, on the subpage `/customers` (`https://app.natconf.dev/customers`).
     - If your table has a different name, replace `customers` with that table's name.
     - If you want multiple tables to be accessible, copy the entire `location /[tablename]` block and paste it in as often as you need, replacing `[tablename]` with the names of the tables.
 
-Be sure to change `denizk0461.dev` to your own domain, as this will otherwise not work.
+Be sure to change `natconf.dev` to your own domain, as this will otherwise not work.
 
 ### Configure the Database
 
@@ -113,7 +113,7 @@ Once you have the database running, we need to create a table to store data in.
 
 You're best off following [the official guide for PostgREST](https://docs.postgrest.org/en/v14/tutorials/tut0.html#step-3-create-database-for-api). Important steps: create the schema, name it `api` (that's the publicly-accessible schema because we set `PGRST_DB_SCHEMAS: 'api'` in the `compose.yml`), create a table (name has to start with `api.` but can be anything after that, e.g. `api.customers`), insert test data, create the roles `web_anon` and `authenticator` and then quit by typing `\q`. That's all. Welcome back!
 
-You can now access the database data on `https://app.denizk0461.dev` (if you replace my domain with yours). Keep in mind that the PostgREST guide only grants read access (GET) to the database; in order to POST data to the database, you need to grant `INSERT` privileges to `web_anon`: `grant insert on api.customers to web_anon;`.
+You can now access the database data on `https://app.natconf.dev` (if you replace my domain with yours). Keep in mind that the PostgREST guide only grants read access (GET) to the database; in order to POST data to the database, you need to grant `INSERT` privileges to `web_anon`: `grant insert on api.customers to web_anon;`.
 
 If you want a kind voice to guide you through this process, I found [Ian Wootten's video on setting up PostgREST](https://youtu.be/RxuofiZNhtU) to be very nice to follow along.
 
@@ -137,10 +137,10 @@ if (response.ok) &#123;
 }
 </pre>
 
-In this example, I set up two environment variables: `API_HOST` and `API_DB`. Those are secrets that won't be published to your Git provider when you push your changes (if your .gitignore is set up correctly!). `API_HOST` is the fully-qualified domain, e.g. `https://app.denizk0461.dev`, and `API_DB` is the name of the table, e.g. `customers`. Doing this is not necessary, but it's good practice to keep secrets, especially once you get to the stage of needing passwords or authentication keys. If you want to use environment variables, create a file named `.env` in the root directory of your application, add the variables as such:
+In this example, I set up two environment variables: `API_HOST` and `API_DB`. Those are secrets that won't be published to your Git provider when you push your changes (if your .gitignore is set up correctly!). `API_HOST` is the fully-qualified domain, e.g. `https://app.natconf.dev`, and `API_DB` is the name of the table, e.g. `customers`. Doing this is not necessary, but it's good practice to keep secrets, especially once you get to the stage of needing passwords or authentication keys. If you want to use environment variables, create a file named `.env` in the root directory of your application, add the variables as such:
 
 <pre class="code-block">
-API_HOST="https://app.denizk0461.dev"
+API_HOST="https://app.natconf.dev"
 API_DB="customers"
 </pre>
 
@@ -168,7 +168,7 @@ kit: &#123;
     adapter: adapter(),
     csrf: &#123;
         trustedOrigins: [
-            "https://app.denizk0461.dev"
+            "https://app.natconf.dev"
         ],
     },
 },
@@ -206,7 +206,7 @@ I'm going to prove why you should avoid generative AI at all costs. Let's go thr
 
 1. Use Relative Form Actions
 
-This 'fix' describes using relative paths to access form URLs. Instead of `https://app.denizk0461.dev/customers`, I should just use `/customers`.
+This 'fix' describes using relative paths to access form URLs. Instead of `https://app.natconf.dev/customers`, I should just use `/customers`.
 
 This doesn't work.
 

src/routes/blog/2026/0325.md

@@ -14,7 +14,7 @@ To create the font, I used [FontForge](https://fontforge.org). Finding this tool
 
 ## Download & use
 
-[Download the font here](https://files.denizk0461.dev/public/lightyears.woff2). It's in the web-optimised `woff2` format and has most characters stripped to minimise its file size – it's less than 20 kilobytes in size! Uppercase and lowercase letters are the same.
+[Download the font here](https://files.natconf.dev/public/lightyears.woff2). It's in the web-optimised `woff2` format and has most characters stripped to minimise its file size – it's less than 20 kilobytes in size! Uppercase and lowercase letters are the same.
 
 For use on your website, put the font into your resources/static/similar folder and then add this block of code to your CSS file: