Deploy Application from Git
The Deploy Application from Git method allows you to deploy an application directly from a Git repository. This method is useful for teams that manage their code in version control systems and want deployments to be triggered directly from their repositories.
Step 1: Open Deploy Application
From the dashboard, navigate to Applications and select Deploy Application.
Step 2: Select Organization
Choose the organization where the application will be deployed.
Step 3: Configure Application Details
Provide the required deployment information such as the application name and other configuration details required by the platform.
Step 4: Select Git Repository
Choose Git Repository from the available deployment methods.
Step 5: Connect Repository
Enter the required repository details such as the Git provider, repository URL, and branch name.
Step 6: Configure Repository Settings
Provide the required repository configuration fields so the platform can access the project.
1. Git Provider & Repository URL
Provider: Select the Git provider where the repository is hosted. Supported providers include GitHub, GitLab, and Bitbucket.
Repository URL: Enter the Git repository URL containing the application source code. Once entered, the platform validates the repository connection.
Branch: Select the branch from which the code should be pulled during deployment.
2. Personal Access Token (PAT)
There is an optional field for Personal Access Token.
When to use it: This field is only required when deploying from a private repository. If the repository is public, the platform can validate it without a PAT.
If the repository is private, you can create a PAT secret or select an existing one from the platform vault.
3. Source Security Scan (SAST)
This is an advanced security feature used for enterprise-grade deployments.
SAST (Static Application Security Testing): By clicking Run Security Scan, the platform scans the repository source code for vulnerabilities such as insecure code patterns or exposed credentials.
Secrets Detection: This feature helps detect sensitive information such as API keys or tokens that may have been accidentally committed to the repository.
SCA (Software Composition Analysis): Currently listed as Coming Soon, this feature will analyze project dependencies and identify known vulnerabilities in third-party libraries.
Once the repository configuration is complete, click Continue.
Step 7: Configure Build Settings
The next step is to configure how the application should be built, so to continue to next phase of build click on Continue.
This section allows you to configure the following settings:
1. Ports Configuration
Define the ports used by the application.
Internal Port: The port used inside the container where the application runs.
External Port: The port exposed externally to allow users to access the application.
2. Environment Variables
Environment variables allow you to configure runtime settings for the application.
These variables are often used to configure environment modes, API endpoints, or application settings without modifying the source code.
You can add additional variables by selecting Add Variable.
3. Build Configuration
This section defines how the container image should be created.
Auto Dockerize with Runtime
This option automatically generates a Dockerfile based on the selected runtime environment.
Supported runtimes include Node.js, Python, Go, Java, Ruby, PHP, Rust, and .NET.
Add Custom Dockerfile
If your repository already contains a Dockerfile, you can configure the platform to use it directly to build the container image.
Specify Dockerfile Path
Provide the path to the Dockerfile in your repository so the platform can locate it. The platform will then use this Dockerfile to build your application.
Once the build configuration is completed, click Continue.
Step 8: Start Build
After Security Source Scan click on Start Build to start the build process.
Once it has been built, we can click on Optimize Docker Image to optimize the Docker image. Further once all this has been done, we can click on Continue to deploy the application.
Step 9: Configure Resources
This section defines the compute environment, scaling, and deployment logic for your application. Basically this section allows you to configure:
- CPU allocation
- Memory allocation
- Storage configuration
- Networking settings
Infrastructure & Resources
Regions: Select the geographic data center for your deployment.
Resource Type: Choose the compute hardware (CPU, GPU, TPU, etc.) for your workload.
Resource Requests / Limits: Set the guaranteed baseline resources and hard usage caps for CPU and memory.
Deployment Strategy & Workload
Strategy: Choose how to roll out updates (e.g., Rolling, Canary, Blue-Green).
Workload: Define the execution type, such as a standard Deployment, CronJob, or StatefulSet.
Storage & Scaling
Deployment Mode: Enable primary or backup failover configurations.
Persistent Volume: Configure optional storage size and its internal mount path.
Scaling: Specify the number of active replicas (1–10) per region.
If a template was selected earlier, recommended values may already be preconfigured.
Step 10: Review Deployment Configuration
Before deployment, the platform displays a ** Pre-Deploy Security Checks** for security checks we can click on Run Security Pipeline, along with thatsummary page showing all previously selected options for confirmation.
This summary includes:
- Application name
- Organization
- Repository configuration
- Branch selection
- Build configuration
- Ports
- Environment variables
- Resource allocation
If everything looks correct, proceed with deployment. Otherwise, you can select Back to modify the configuration.