Builds
Table of Contents
When you create a new project or push a new commit to a project on Epycbyte, you initiate a deployment.
A deployment is made up of a few steps:
The build step
Running checks
Assigning a domain
Build process
You can initiate a Epycbyte deployment in two ways:
with Epycbyte CLI or by pushing changes to a connected Git repository on GitHub, GitLab, or Bitbucket.
It's also possible for deployments to be initiated through an integration using Epycbyte REST API.
Depending on how you initiate the build, Epycbyte may put it in a queue to ensure we build things in the right order and only build the most recent deployment.
Build step
The build container will receive a request that there is a job available.
The build container is a Docker container that uses an Amazon Linux based image and includes some pre-installed packages.
Epycbyte first authenticates and inspects the request to confirm its authenticity and your permission to create the deployment to protect against unauthorized access and loss of integrity.
At this point, Epycbyte also validates the Epycbyte configuration in the epycbyte.json file.
Build container
The build container runs in a few regions on our Edge Network—you can determine which one by viewing your build logs.
If you use Git to initiate your deployment, Epycbyte performs a shallow clone on your Git repository to fetch the most recent Git commit history.
CLI deployments won't do this step—they'll follow the flow in the next step.
Build process
A POST request is made containing the project’s files to be uploaded (without these ignored files) to a scalable, secure, and highly durable data storage service.
Once the source files have been uploaded, another POST request is made to start the build and deployment process.
Epycbyte will check for an existing build cache key. If it finds one, it will restore the previous build cache.
Build output
The build container creates a build output that runs on one of Epycbyte's supported runtimes and provisions resources such as:
Serverless Functions for handling API routes and server-side rendered pages
Edge Functions for Middleware and other functions using the edge runtime
Optimized Images
Static output
Build limits
The maximum duration of the build is 45 minutes.
When the limit is reached, the build will be interrupted and the deployment will fail.
Pricing
Manage and Optimize pricing
Metric Description Priced Optimize
Build Time The amount of time your Deployments have spent being queued or building Additional concurrent builds Learn More
Number of Builds How many times a build was issued for one of your Deployments No N/A
Build Process
When you create a new project or push a new commit to a project on Epycbyte, you initiate a deployment. A deployment consists of several steps, including the build step. This guide focuses on understanding how the build process works when creating a Epycbyte Deployment.
Understanding the Build Step
The build step is a critical part of the deployment process. It involves validating and building your source code, outputting all assets into storage. Epycbyte supports various frameworks and will automatically configure the build settings for the most common configurations. If you have specific requirements, you can adjust build, output, and environment variables when creating or modifying your project.
Initiating a Build
You can initiate a deployment in two ways:
- Using the Epycbyte CLI.
- Pushing changes to a connected Git repository (GitHub, GitLab, Bitbucket).
Deployments triggered by integration using the Epycbyte REST API are also possible. Depending on how you initiate the build, Epycbyte may queue it to ensure builds are processed in the correct order and only the most recent deployment is built.
Build Container Details
The build container is a Docker container based on Amazon Linux and includes pre-installed packages. It runs in multiple regions of Epycbyte's Edge Network, which you can view through your build logs. The container authenticates requests to ensure they are legitimate and verifies your permission to create the deployment, protecting against unauthorized access.
Epycbyte creates a specific resource allocation for each build that cannot be increased. Each build cache can store up to 1 GB of data and is retained for one month. Currently, you cannot customize which files are cached.
Build Limits
The maximum duration of a build is 45 minutes. If this limit is reached, the build will be interrupted, and the deployment will fail. For more details, see "Cancelled Builds due to limits."
This article provides a comprehensive overview of Epycbyte's build process, including how builds are initiated, container details, caching, and build limits.