Publishing to Lantern Hub

1. Create your Hub address #

An address must be 2–40 lowercase letters, digits or hyphens, beginning with a letter or digit. Reserved or occupied names cannot be claimed by ordinary creators. Creating a local folder does not reserve a Hub address.

1. Open the creator dashboard and sign in with GitHub.
2. Create a site with your chosen address, title and description.
3. Use the same address as your local site when uploading from Lantern.

2. Create an upload key #

Open the site’s management page and generate a key. Treat it as a secret. It permits draft uploads for that site, not publication, moderation or access to other sites. Revoke an exposed or unused key from the dashboard. Do not paste it into page JSON, Lua source or screenshots.

3. Upload your local files #

Despite the command name, this uploads a draft only. You must still publish in the web dashboard. The equivalent editor action is Upload Hub draft.

On first use, paste the matching site key into the hidden prompt. Lantern stores it in /lantern-data/private/hub-<name>.json, bound to the configured Hub origin. If that saved key is revoked, remove only that site’s saved key file to be prompted for a replacement. Never distribute this private directory.

The upload scans page JSON and app.lua and excludes data directories. You can alternatively upload a ready-made JSON package from the web dashboard.

lantern publish my-first-site

4. Review and publish #

A Lua syntax or runtime error may only appear when that route executes. Local Validate site and Preview locally help catch mistakes, but cloud libraries and execution limits differ.

1. Open the draft in the Hub dashboard.
2. Review the uploaded files and static preview. A source preview does not execute Lua.
3. Publish the intended version.
4. Visit hub://my-first-site/ from Lantern and test every route and form.

Updating and availability #

Edit locally, upload a new draft, review and publish again. Uploading a draft alone leaves the published version unchanged. Site data persists independently of code versions.

After publication, shut down the originating computer and visit from another computer to confirm independent cloud hosting. HTTP access to lantern.thultz.dev must still be allowed by the browsing computer’s Minecraft server.

Administrative disabling, deletion, account bans and restrictions can prevent browsing, uploading or publication. Read your notification inbox for moderation decisions.