Thanks! I think this is the one.

I love the idea of adding a default template, might try that!

It just dynamically reads the date, touches the file in case it doesn't exist, and opens it up. It also opens the directory as the workspace so that I can see past notes in the sidebar.

Yeah, I want all the configuration to live in the repo.

Ideally the system would be able to recognize if files changed since the last build, I already do this for e.g. vercel sites in a monorepo and it works fine.

Coolify looks good but seems to be aimed more for public sites so leaves auth to the application layer? I'm hoping to have one server manage deployment, hosting, and auth.

frontend + backend ideally, but even just static apps (with a build step) would work.

one password across all, or else oauth with approved users on a per-app basis

subdomains under the same domain would be ideal, i.e. repo/foo would map to foo.mydomain .com

The author Jon Ronson has done a few limited series in podcast form that are top notch.

And certainly no side-effects!

Nice write up too!

The dots came out nicely, I’m surprised not to see artifacts of the spiral.

www.rupertbrooks.ca/SketchyMachi...