"CMS-free" as in "does not depend on additional software to manage content". Postgres and S3 through MinIO are my preferred choices, but you can change that to anything you'd like to use instead.
Glad you like the in-place editing. I'm also for the first time happy with the experience. You can press CMD+E for editing and CMD+S saving, and there's no layout shift, so it's really convenient for quick edits. :)
"CMS-free" as in "does not depend on additional software to manage content". Postgres and S3 through MinIO are my preferred choices, but you can change that to anything you'd like to use instead.
Cool! Postgres and an S3-compatible object store area are both listed as requirements, so you may want to update that.
So by "does not depend on additional software", does that means I can just use the filesystem?
Comments
The repo notes that persistence requires editors to in with the (shared?) admin user and password.
Although the pitch is "CMS-free", this is a Postgres- and S3-backed content management system.
The in-place editing is extremely cool.
"CMS-free" as in "does not depend on additional software to manage content". Postgres and S3 through MinIO are my preferred choices, but you can change that to anything you'd like to use instead.
Glad you like the in-place editing. I'm also for the first time happy with the experience. You can press CMD+E for editing and CMD+S saving, and there's no layout shift, so it's really convenient for quick edits. :)
Cool! Postgres and an S3-compatible object store area are both listed as requirements, so you may want to update that.
So by "does not depend on additional software", does that means I can just use the filesystem?
You could just use the filesystem indeed.
why not just have a tonne of html files on disk?? I'm confused at why this requires a sophisticated backend.
Why is Postgres needed here? Couldn't everything be saved in static files published in S3 or any other CDN?