Welcome to the Incode Labs Application Platform. This site provides templates and resources for deploying applications to the Incode Labs environment.
To create and deploy a new application to the Incode Labs environment, follow these steps:
Start by creating a new GitHub repository for your application.
You'll need three key files to deploy your application:
Use this script to set up the template files:
#!/bin/bash # Create directories mkdir -p .github/workflows # Download templates curl -L https://bootstrap.labs.incode.com/templates/labspec.yaml -o labspec.yaml curl -L https://bootstrap.labs.incode.com/templates/github-workflows/deploy.yml -o .github/workflows/deploy.yml echo "Templates downloaded successfully!"View Detailed Instructions
Example Application: See a complete working example at github.com/IncodeTechnologies/incode-labs-demoapp
Update the templates with your application's specific details:
Commit and push your changes to the main branch. The GitHub Actions workflow will automatically:
Your application will be available at https://{app_name}.labs.incode.com
Templates to help you quickly set up new applications:
Modules used by the deployment process:
You can configure the CPU and memory resources for your application using the instance_size field in your labspec.yaml:
| Size | CPU | Memory | Use Case |
|---|---|---|---|
small (default) |
0.25 vCPU | 512 MB | Simple APIs, lightweight services |
medium |
0.5 vCPU | 1 GB | Moderate workloads |
large |
1 vCPU | 2 GB | Heavier processing |
xlarge |
2 vCPU | 4 GB | Video processing, ML inference |
xxlarge |
4 vCPU | 8 GB | Heavy compute workloads |
Example:
app_name: video-processor image: video-processor container_port: 8080 instance_size: xlarge # 2 vCPU, 4GB RAM for video processing
Note: Larger instance sizes will incur higher AWS costs.
When you no longer need your application, you can destroy all its resources:
labspec.yaml file and add destroy-app: trueExample:
app_name: myapp image: myapp-image container_port: 8080 destroy-app: true # This will trigger destruction of the application stack
If you encounter issues with your deployment: