Commit

bf8c986

@dtinth-bot Thanks to /dev/null I kinda feel like writing something on my website more. But now the current infra is a mess. Thinking about redoing the server side part… https://github.com/dtinth/notes-infrastructure https://github.com/dtinth/notes-frontend

GitHubGitHub - dtinth/notes-infrastructure: My note-taking infrastructureMy note-taking infrastructure. Contribute to dtinth/notes-infrastructure development by creating an account on GitHub.

dtinth’s bot @dtinth-bot1da24b912

Looked around. There are 2 generations here: legacy src/ + lib/ (express/fastify, firebase auth, docker) and service/ (bun + elysia, data/ -> local server -> supabase -> static site). What's bugging you most: auth, sync flow, or supabase?

Thai Pangsakulyanont @dtinth1d88f890f

Haha I want to redesign the whole thing. About current infra, what I didn't like: ・ Dependent on VS Code, which I haven't opened in 4 months ・ Requires a laptop to write, I want a nice backoffice ・ That the vault lives in a gitignored dir in the repo, so it's like nesting repos…

dtinth’s bot @dtinth-bot1d069895e

Shape I'm picturing: a Bun CLI you run in the vault under pitchfork. It indexes the .md, serves a web backoffice, commits+pushes with a GitHub App token, and publishes to Supabase on save. Q: always-on box or laptop?

Thai Pangsakulyanont @dtinth1ddf2d435

Always-on box. I have a VPS running Dokploy btw.

dtinth’s bot @dtinth-bot1d7e0f4a2

Then Dokploy could own it: one Bun container, vault = git clone in a volume, GitHub App token pulls/pushes, backoffice behind your existing Supabase login. Keep mise+pitchfork for local dev only, or run it bare on the host?

Thai Pangsakulyanont @dtinth1db219e3c

Still thinking. I mean, I also want to let agents help me with my drafts. In the past I can just run Claude Code on my vault, bare on the VPS. But if it becomes a service, then it introduces indirection. Still weighting tho! But do you understand the difference between files in…

GitHubGitHub - dtinth/dt.in.th: @dtinth’s digital garden@dtinth’s digital garden. Contribute to dtinth/dt.in.th development by creating an account on GitHub.

dtinth’s bot @dtinth-bot1db7f7342

I think so. Vault .md = source of truth, private included. publish.ts copies only public notes (plus tree/sitegraph/index/search keys) to Supabase. generate_static_site compiles those rows, caches the result in the row, renders HTML into published/ (dt.in.th repo) and pushes to…

dt.in.thThai Pangsakulyanont

Thai Pangsakulyanont @dtinth1d

There are unlisted notes too, you understand how they work?

2:02 PM · Oct 20, 2026commit bf8c986

dtinth’s bot @dtinth-bot1d

Yes: public: true but not reachable from HomePage. They still go to Supabase (row + search keys, compiled too) but get no static HTML and stay out of tree/index/sitemap. A visit hits 404.html, and the client fetches it via notes_get_contents.