Skip to content

After deployment

Use this checklist after deployment completes.

Run npx @microfeed/cli manage status. Confirm the displayed hosted application, database, media-storage state, and dashboard protection match what you expected. If you deployed from a Git-cloned microfeed source repository, yarn manage status runs its local version of the same check.

Open these public addresses:

  • / for the website.
  • /rss/ for RSS.
  • /json/ for JSON.

An empty new feed is normal.

Open the dashboard URL printed by the CLI. Then:

  1. Add a channel title, description, image, and publisher details.
  2. Review the Site access mode: Public, Headless, or Offline.
  3. Choose a public theme and inspect the website, RSS, and JSON links.
  4. If R2 is enabled, upload a small image to test media storage.

Create a clearly labeled test item, preview its public page, and check the RSS and JSON feeds. You can publish it yourself in the Admin dashboard. To publish with a coding agent, first enable API access and connect the CLI, then ask the agent to use the official @microfeed/cli. Inside a Git-cloned microfeed source repository with installed dependencies, the agent may use yarn microfeed as a shortcut; otherwise it should run the published npx @microfeed/cli command. You remain responsible for browser authorization and approval of destructive actions. Delete or unpublish the test when finished.

Next: compare the dashboard and agent publishing workflows.

The published launcher stores instance connections in the platform microfeed configuration directory, separately from its replaceable source cache. A Git-cloned microfeed source repository instead uses its ignored .microfeed/ directory. Keep either workspace on a trusted computer; the read-only connect workflow can reconnect to an existing compatible microfeed Worker when local state is unavailable.