What problem does it solve?
Manage and standardize Dojo project configuration to avoid broken builds, misconfigured deployments, leaked secrets, and inconsistent world settings across environments so teams can reliably build and deploy Starknet games and contracts.
Core Features & Use Cases
- Scarb.toml management: Add or update package dependencies, target settings, and external contract mappings.
- Profile configuration: Create and modify dojo_dev.toml and dojo_<profile>.toml files for development, staging, and production environments.
- World, namespace, and permission setup: Configure world metadata, namespaces, writers, and owners to prepare a project for deployment and runtime access control.
- Use Case: Add the Origami library to dependencies, create a mainnet profile with keystore-based secret handling, and generate a production-ready world configuration for sozo migrate.
Quick Start
Update my Dojo configuration to add the origami dependency and create a mainnet profile with keystore-based secrets for production deployment.