Lume CMS remote storage

[kuboon]

Lume CMS supports multiple storage backends:
https://github.com/lumeland/cms/tree/main/storage

They work perfectly in the CMS editor, but currently it is difficult to run lume build using these storages.

My idea is that the lume_cms plugin should iterate over documents, collections, and files, fetch all entries via the storage API, and then register them into site.pages (as remoteFile, or something similar).

My current problem is the previewUrl on the CMS edit page. It seems that the Lume rebuild process is entirely dependent on filesystem watching. The default previewUrl function

lume/plugins/lume_cms.ts

Lines 59 to 77 in 98f49d7

	cms.options.previewUrl ??= function previewUrl(
	path: string,
	data: unknown,
	hasChanged?: boolean,
	): undefined | string | Promise<string | undefined> {
	if (hasChanged) {
	return new Promise((resolve) => {
	site.addEventListener("idle", () => {
	resolve(previewUrl(path, data));
	}, { once: true });
	});
	}
	for (const page of site.pages) {
	if (page.src.entry?.path === path) {
	return site.url(page.data.url);
	}
	}
	};

waits for the idle event, but GitHub storage does not modify the local filesystem. As a result, it does not trigger a Lume rebuild and the idle event is never fired.

Would it be a reasonable approach to explicitly call site.update(files); on CMS save?

If you have any plans or ideas regarding this, I would be happy to hear your thoughts.

[oscarotero]

Lume and LumeCMS are different things. The CMS is used in dev mode (with deno task serve) and this plugin setup the CMS in the Lume server but not in the build for production (deno task build).

The purpose of the storages in LumeCMS is to have the ability to modify files that are not available locally, but it doesn't mean that Lume can't access to these files locally. For example, in this repo I have the GitHub storage configured to manage the files of other repository that could be a Lume site (it's not the case but it could be) so these files would be loaded by LumeCMS remotely but Lume would read them from the filesystem.

If your files are accessible publicly on GitHub, you can add them in Lume without any configuration.

Private files or other Git providers like GitLab or Codeberg are not supported (but I think it could be feasible, I created this package some time ago and it could be extended with more adapters and used to load remote files by Lume).

[kuboon]

My goal is to deploy site with CMS on "deno deploy (EA)"

• /admin/ opens CMS with auth
• / shows the site without drafts
• use KvStorage or private github repo for drafts (public repo is not suitable for drafts, IMO)
• CMS edit pages show preview (even if it's draft)

I understand your current views and outlook.

I'll hack away at my goals. Thank you.

[kuboon]

I will make draft page have some random strings in url and build the page.
It's enough if it's not linked and unlisted from sitemap.
This way solves the preview problem.