Commit

60056d5

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...
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…
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.
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…
Removed (b1e104e). What it configured (run user = vault owner's uid, /vault bind mount, /data volume, env vars) is now listed in the Dockerfile, and the defaults moved into ENV. Also CI is green: typecheck, 29 tests including integration against supabase start in Actions, bundle, docker build. https://github.com/dtinth/notes-infrastructure/actions
GitHubAll Workflow Runs · dtinth/notes-infrastructureMy note-taking infrastructure. Contribute to dtinth/notes-infrastructure development by creating an account on GitHub.

commit 60056d5