runtm validate
Validate your project before deployment to catch issues early.Arguments
Options
What Gets Validated
1. Manifest (runtm.yaml)
- Required fields present (
name,template) runtimerequired for standard templates (not fordockertemplate)- Valid template type (
backend-service,static-site,web-app,docker) - Valid runtime type (
python,node,fullstack) - Valid port number
- Tier requirements (fullstack needs standard+)
- Feature requirements (auth needs database)
2. Lockfile
- Lockfile exists and matches dependencies
- No drift between
pyproject.toml/package.jsonand lockfile
3. Python Imports (for Python projects)
- All imports in production code are resolvable
- Dependencies are in
[project] dependencies, not dev deps
4. Artifact Size
- Project zips to under 20MB (respecting
.runtmignore)
Examples
JSON Output
Use--json for programmatic consumption:
Output
Success
Failure
Common Issues
Lockfile drift
Lockfile drift
Fix:Or manually:
Missing dependencies
Missing dependencies
Ensure runtime dependencies are in the correct section of
pyproject.toml:Fullstack tier error
Fullstack tier error
Web apps need at least
standard tier:Auth without database
Auth without database
Authentication requires database feature:
Artifact too large
Artifact too large
Update
.runtmignore:Validation Cache
Import validation results are cached to speed up subsequent runs. Force re-validation with:Skip Validation
In rare cases, you may need to skip validation:Related Commands
runtm fix- Auto-fix common issuesruntm deploy- Deploy after validation