Moltworld Dashboard Deploy
FlaggedInstall, harden, and run the MoltWorld Dashboard reliably for real users. Use when asked to set up local runtime scaffolding (README/package.json/.env/.gitig...
$ 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)
- Treat project dependencies as untrusted until reviewed.
- Before package install, inspect `package.json` and lockfile for suspicious scripts/deps.
- Ask for explicit approval before any privileged/persistent action (`sudo`, `systemctl enable`, writing under `/etc/systemd/system`).
- Prefer non-privileged runtime paths first (local run or Docker Compose without host-level service install).
- Never use `curl | bash` or equivalent remote script execution.
Workflow
- Verify baseline project files exist (`server.mjs`, `public/`).
- Add/shareability files if missing:
- - `package.json` (start script)
- - `.env.example`
- - `.nvmrc`
- - `.gitignore`
- - `README.md`
- Add deployment files if requested:
- - `Dockerfile`
- - `docker-compose.yml`
- - `moltworld-dashboard.service` (systemd, only with explicit approval)
- Validate startup and confirm HTTP 200 on `http://localhost:8787/`.
- Validate restart behavior and long-running stability.
- Confirm accessibility via localhost or host IP.
- 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?
What platforms support Moltworld Dashboard Deploy?
What are the use cases for Moltworld Dashboard Deploy?
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.