Commit
5857b5d
@dtinth Done (69db93a, local). Slight change of plan: no repacking needed. The browser assets already ship as notes-frontend release tarballs, so
notes build downloads the pinned @notes/client + @notes/compiler tgz once, caches them in ~/.cache/notes, and copies compiler/,âŚYes please. It's already in ghq. Access to both repos granted. For notes-frontend, since we will not be making any interface change, you may make changes in a PR to main directly and automatically merge when builds pass.
@dtinth PR is up: https://github.com/dtinth/notes-frontend/pull/2 . Build and compiler tests pass locally, and the dev-build message is gone. But CI only runs on push to main, so the PR has no checks, and my merge got blocked by my permission guard. Can you merge it? I will watchâŚ
GitHubUse Vue's production build in the compiler by dtinth-claw[bot] ¡ Pull Request #2 ¡ dtinth/notes-frontendThe compiler aliased vue to vue.runtime.esm-browser.js, the dev build, which prints "You are running a development build of Vue" whenever it loads. This shows up every time the compiler r...
I took a look. I think that was a good reason for using a development build because when there is a build failure, the stack trace is readable. Is the dev notice suppressable without hijacking console?
@dtinth Yes, without hijacking console. Only the esm-browser build prints that notice. The esm-bundler build has the same dev mode when NODE_ENV is "development", and no notice. PR #2 updated: alias to vue.runtime.esm-bundler.js and define NODE_ENV=development. Same [Vue warn]âŚ
GitHubUse Vue's production build in the compiler by dtinth-claw[bot] ¡ Pull Request #2 ¡ dtinth/notes-frontendThe compiler aliased vue to vue.runtime.esm-browser.js, the dev build, which prints "You are running a development build of Vue" whenever it loads. This shows up every time the compiler r...
@dtinth Main build passed, release v0.0.261020163032 is out. Bumped it on
next (local), rebuilt dist/notes.js, and a clean-dir run builds the example site with no Vue notice.So how's the project status? Send me an infographic.
@dtinth Foundations done: spec, single-file CLI, assets, Vue fix. Next up is parity with legacy, then plan/apply. Want me to push
next and start on parity?I am thinking about deployment and start doubting my own decisions. With Dokploy, deploying a new version of the server is just a matter of pushing to the repo. Dokploy also allows bind mount, so I can bind mount the vault into the server container. Only uid needs to match. WhatâŚ
I think it's better. It keeps what mattered in Q1 (the vault stays a plain dir on the host, so Claude Code still works in it bare) and drops the part I liked least: building a release pipeline just to deploy.
What changes:
- Q25: no bundled-JS release needed for the server. AâŚ
Sounds great.
@dtinth Updated docs/SPEC.md for Dokploy + bind-mounted vault, with the CLI as a thin API client (f16dad0, local). Still waiting on a yes to push
next and start on legacy parity.Yes, pls push and start on legacy parity!
@dtinth Parity done and pushed: https://github.com/dtinth/notes-infrastructure/commit/0e36dcf
bun run parity takes the 466 .md notes from the live dt.in.th repo as a vault and builds into a copy of it:
- tree.json, sitegraph.json, index.json, sitemap.txt, recent.xml, every .mdâŚGitHubReach parity with the legacy static site output ¡ dtinth/notes-infrastructure@0e36dcfPorts note indexing, the public tree, sitegraph, search index, search keys and the full static site build (pages, .md copies, alias pages, 404, api/*, RSS, CNAME and friends) from legacy. `bun run...
Yes please!
On it: plan/apply against Supabase, behind an interface with an in-memory fake and tests. No live Supabase access here, so I will test against the fake and leave a read-only
notes plan for you to run against the real one.You have rootless Docker. Can you work on this autonomously and update progress as you go?
4/7 done (15ae7d1): vault auto-sync. Commits after 5 quiet minutes, pull --rebase, push, and pulls every 15 min too. On conflict it aborts the rebase (the working tree is untouched) and pauses until POST /api/sync/retry. GitHub App tokens are minted per repo and passed as aâŚ
5/7 done (489c721): Dockerfile + docker-compose.yml for Dokploy. Tested in rootless Docker against local Supabase: a note saved over the API was auto-committed and pushed to the vault remote, and the file is owned by the host user. Applying it made the container clone the siteâŚ