Skip to content

Moltworld Dashboard Deploy

Flagged

Install, harden, and run the MoltWorld Dashboard reliably for real users. Use when asked to set up local runtime scaffolding (README/package.json/.env/.gitig...

204 downloads
$ Add to .claude/skills/

About This Skill

# MoltWorld Dashboard Deploy

Standardize this workflow to make `moltworld-dashboard` easy to run and operate safely.

Runtime requirements

  • Required binaries:
  • npm
  • docker
  • docker-compose
  • Optional (privileged persistence path only):
  • systemd
  • sudo

Safety gates (mandatory)

  1. Treat project dependencies as untrusted until reviewed.
  2. Before package install, inspect `package.json` and lockfile for suspicious scripts/deps.
  3. Ask for explicit approval before any privileged/persistent action (`sudo`, `systemctl enable`, writing under `/etc/systemd/system`).
  4. Prefer non-privileged runtime paths first (local run or Docker Compose without host-level service install).
  5. Never use `curl | bash` or equivalent remote script execution.

Workflow

  1. Verify baseline project files exist (`server.mjs`, `public/`).
  2. Add/shareability files if missing:
  3. - `package.json` (start script)
  4. - `.env.example`
  5. - `.nvmrc`
  6. - `.gitignore`
  7. - `README.md`
  8. Add deployment files if requested:
  9. - `Dockerfile`
  10. - `docker-compose.yml`
  11. - `moltworld-dashboard.service` (systemd, only with explicit approval)
  12. Validate startup and confirm HTTP 200 on `http://localhost:8787/`.
  13. Validate restart behavior and long-running stability.
  14. Confirm accessibility via localhost or host IP.
  15. Document runbook steps for operators.

Required file conventions

  • Keep runtime state out of git (`data/state.json`, logs, pids).
  • Keep secrets out of git (`.env`).
  • Default runtime port: `8787`.
  • README must include:
  • - local quick start
  • - Docker run
  • - Docker Compose run
  • - systemd install/enable instructions marked as privileged/optional

Runtime stability checks

Use these checks when service becomes unreachable:

```bash ss -ltnp | grep ':8787' || true curl -I --max-time 5 http://localhost:8787/ ```

If process is down, restart with a supervisor (Docker Compose or approved systemd service) instead of ad-hoc foreground runs.

Troubleshooting quick checks

  • Service down: verify listener on `:8787`.
  • Loop timeouts: increase API timeout and add retries in `postJson`.
  • Process died after exec session: restart with supervisor.

References

  • Deployment/runbook command snippets: `references/commands.md`

Use Cases

  • Install and harden the MoltWorld Dashboard for production users
  • Set up local runtime scaffolding with README, package.json, and .env configs
  • Deploy dashboard applications with proper security and configuration
  • Configure environment settings and dependencies for dashboard hosting
  • Build reliable dashboard deployments with hardened security practices

Pros & Cons

Pros

  • +Compatible with multiple platforms including claude-code, openclaw
  • +Well-documented with detailed usage instructions and examples
  • +Purpose-built for devops & infrastructure tasks with focused functionality

Cons

  • -Requires Docker infrastructure for deployment
  • -No built-in analytics or usage metrics dashboard

FAQ

What does Moltworld Dashboard Deploy do?
Install, harden, and run the MoltWorld Dashboard reliably for real users. Use when asked to set up local runtime scaffolding (README/package.json/.env/.gitig...
What platforms support Moltworld Dashboard Deploy?
Moltworld Dashboard Deploy is available on Claude Code, OpenClaw.
What are the use cases for Moltworld Dashboard Deploy?
Install and harden the MoltWorld Dashboard for production users. Set up local runtime scaffolding with README, package.json, and .env configs. Deploy dashboard applications with proper security and configuration.

100+ free AI tools

Writing, PDF, image, and developer tools — all in your browser.

Next Step

Use the skill detail page to evaluate fit and install steps. For a direct browser workflow, move into a focused tool route instead of staying in broader support surfaces.