Mandu Deployment

Automating Mandu app deployment involves using CI/CD strategies to build with Bun and start the production server. This reduces manual toil and risk by applying repeatable deployment patterns across environments.

Deploying a Bun-native application safely requires environment separation guidance for development, staging, and production. Platform-agnostic blueprints streamline the build and run patterns for reliable releases.

Yes, Mandu applications support multi-platform deployment targets including Docker, Render, Fly.io, and Vercel. This allows flexible hosting choices while maintaining consistent CI/CD automation and security guidance.

Environment separation is necessary when deploying Mandu apps to staging and production to ensure safe releases. Distinct development, staging, and production environments reduce risk and maintain reliable deployment patterns.

To deploy on Render, follow the deployment blueprint to install dependencies, build the app with Bun, and start the production server. This provides a streamlined, deterministic path for releasing your application.

Mandu production deployment requires a SKILL.md frontmatter to define the name, description, metadata, and globs for the Skill Unit. This structure enables deterministic task guidance and supports optional script resources.