〔 2023–2026 〕denizk0461
-Built from commit {version.substring(0, 6)}
+Built from commit {version.substring(0, 6)}
server {
listen 443;
- server_name app.denizk0461.dev;
+ server_name app.natconf.dev;
location / {
proxy_pass http://localhost:3000;
@@ -100,12 +100,12 @@ server {
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) {
}
-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:
-API_HOST="https://app.denizk0461.dev" +API_HOST="https://app.natconf.dev" API_DB="customers"@@ -168,7 +168,7 @@ kit: { adapter: adapter(), csrf: { 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. diff --git a/src/routes/blog/2026/0325.md b/src/routes/blog/2026/0325.md index 4443b85..dbd1977 100644 --- a/src/routes/blog/2026/0325.md +++ b/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: diff --git a/src/routes/blog/feed.xml/+server.ts b/src/routes/blog/feed.xml/+server.ts index 630a45e..7c38cce 100644 --- a/src/routes/blog/feed.xml/+server.ts +++ b/src/routes/blog/feed.xml/+server.ts @@ -4,7 +4,7 @@ import { posts } from "../posts"; const xml = () => `
- As for the server infrastructure: the website is hosted on a Hetzner server instance I am renting. It's a relatively cheap CPX22 node that costs me 7,72€ a month, and besides my website, it's also hosting things such as a Nextcloud instance and a Minecraft server. In order to host and update the website, I wrote a small bash script that pulls the changes from the Git repository, builds the website as a Node server, and then exposes it via Nginx.
+As for the server infrastructure: the website is hosted on a Hetzner server instance I am renting. It's a relatively cheap CPX22 node that costs me 7,72€ a month, and besides my website, it's also hosting things such as a Nextcloud instance and a Minecraft server. In order to host and update the website, I wrote a small bash script that pulls the changes from the Git repository, builds the website as a Node server, and then exposes it via Nginx.
The rat in the bottom right of the screen is property of Insomniac Games. Clicking it will bring you good fortune.
-The style of the webring elements is adapted from a template provided by Rainbow Cemetery for the Gamedev webring. I adapted it into a Svelte component that allows setting the links, emojis, and arrows more easily.
+The style of the webring elements is adapted from a template provided by Rainbow Cemetery for the Gamedev webring. I adapted it into a Svelte component that allows setting the links, emojis, and arrows more easily.
This page uses no cookies as of now. No data will be stored on your device while browsing this website. No trackers are used either – no analytics, not even a visit counter of any kind. Not by a third-party, and currently, none I built myself either.
-The Godot and Unity projects on the apps.denizk0461.dev subdomain may cache compiled shaders on your device, I'm not sure. These files would only be used by your GPU to render visual effects for the game they were compiled for.
The Godot and Unity projects on the apps.natconf.dev subdomain may cache compiled shaders on your device, I'm not sure. These files would only be used by your GPU to render visual effects for the game they were compiled for.
Last updated: 2025-09-10
diff --git a/src/routes/meta/updates/updates.ts b/src/routes/meta/updates/updates.ts index 2396eb6..755b85f 100644 --- a/src/routes/meta/updates/updates.ts +++ b/src/routes/meta/updates/updates.ts @@ -69,7 +69,7 @@ export const entries: UpdateEntry[] = [ date: "2026-02-03", time: "15:48", content: "Now running my own Gitea instance! It now also hosts my website repository.", - link: "https://code.denizk0461.dev/denizk0461/pages", + link: "https://code.natconf.dev/denizk0461/pages", }, { date: "2026-02-02", diff --git a/src/routes/projects/projectn5/devlog/2025/0816.md b/src/routes/projects/projectn5/devlog/2025/0816.md index 8f94978..d64a17c 100644 --- a/src/routes/projects/projectn5/devlog/2025/0816.md +++ b/src/routes/projects/projectn5/devlog/2025/0816.md @@ -4,19 +4,19 @@ let builds: LinkEntry[] = [ { text: "2023-10-07 (Protagonist #1)", - link: "https://files.denizk0461.dev/public/projectn5/2023-10-07.zip", + link: "https://files.natconf.dev/public/projectn5/2023-10-07.zip", }, { text: "2023-12-23 (Protagonist #2)", - link: "https://files.denizk0461.dev/public/projectn5/2023-12-23.zip", + link: "https://files.natconf.dev/public/projectn5/2023-12-23.zip", }, { text: "2024-03-25 (Protagonist #3 with jump animations)", - link: "https://files.denizk0461.dev/public/projectn5/2024-03-25.zip", + link: "https://files.natconf.dev/public/projectn5/2024-03-25.zip", }, { text: "2025-08-16 (Laura era) [same build as the web version]", - link: "https://files.denizk0461.dev/public/projectn5/2025-08-16.zip", + link: "https://files.natconf.dev/public/projectn5/2025-08-16.zip", }, ]; @@ -33,9 +33,9 @@ The good news is that I'm done with all of this! The bachelor's thesis in partic I decided to upload some playable builds of **Project N5**! Now that the website is running on my own server instead of being hosted by GitHub or Codeberg, I have a lot more freedom here. -The game, in its state from 2025-05-16 (before the reboot), is available to play in-browser [right here!](https://apps.denizk0461.dev/projectn5) It's not a terribly great experience, though. Loading times are significantly longer and shader compilation regularly freezes the game for longer than in a locally-saved copy. Some shaders are also not functioning as intended, though this only has a minor visual impact. The game was never optimised to work on the web, after all. +The game, in its state from 2025-05-16 (before the reboot), is available to play in-browser [right here!](https://apps.natconf.dev/projectn5) It's not a terribly great experience, though. Loading times are significantly longer and shader compilation regularly freezes the game for longer than in a locally-saved copy. Some shaders are also not functioning as intended, though this only has a minor visual impact. The game was never optimised to work on the web, after all. -I've also uploaded old builds of the game [here](https://files.denizk0461.dev/public/projectn5). You'll find the following builds, one for each protagonist: +I've also uploaded old builds of the game [here](https://files.natconf.dev/public/projectn5). You'll find the following builds, one for each protagonist: