Use case or problem
More control over published content. Currently, Obsidian Publish service is very opinionated (Cloudflare & domain DNS setting filling, no preview until published, proxy settings), and i’d love to generate files locally so i can upload where i want to, have more control over editing output, and choosing where to upload files.
I also like the idea of having ownership over created publish content, as a web dev it’s strange to only see output when live. With files locally, i could expand publish capabilities as needed (for example use multiple CSS snippets instead of single publish.css file)
FTP forum posts linked below mentions that Publish content is generated on demand and cached, so this might be more involved because publish code would need to run locally as well.
Proposed solution
Obsidian Publish should have a local folder as export option, or plugin option to choose how output works.
Current workaround (optional)
I download files once published to inspect how generated output works. However, it’s too tedious to do custom domains and such my way, so i’m currently sticking to Publish URLs with old fashioned redirect and considering this “blocked” until that’s resolved.
Related feature requests (optional)
forum.obsidian.md/t/ftp-access-for-obsidian-publish/94534