Builds and build minutes

When you deploy from Git, Plexivo App Runner clones your branch, builds an image, signs it and releases it. Each build runs in its own isolated sandbox.

How Plexivo builds your code#

• With your Dockerfile. If the repository has a Dockerfile at its root, Plexivo builds it as it is. This gives you full control.
• Without one. Plexivo detects your language and framework, installs your dependencies, builds and sets the start command.
• Static sites. If the project builds files but has no server, such as a React or Vue front end, Plexivo serves what it built. It looks for index.html in dist, build, out, public, _site or the root, and sends unknown paths to index.html so client-side routes work.

Listen on PORT#

Plexivo sets the PORT environment variable and sends traffic to it. Read PORT in your app and listen on 0.0.0.0. Unless your image declares another port with EXPOSE, it is 8080.

const port = process.env.PORT || 8080;
app.listen(port, '0.0.0.0');

Follow a build#

The app’s Deployments tab lists every build with its Build status, Commit, Author, Duration and Build minutes. A failed build shows why, with the build output. Below the builds, Serving releases shows what is actually serving.

A build that succeeds is not live until its instances pass their health check.

Build minutes#

Each plan includes build minutes every month. A build minute is a started minute of the build’s own running time: fetching the code, building and pushing the image. Time waiting in the queue is never billed, and neither is copying a container image or a build Plexivo lost.

Minutes beyond your plan’s are charged to your wallet per minute; the price is on the pricing page. When your included minutes are used up, a build starts only if your wallet can pay for your plan’s longest build.

These are the defaults. Your organisation’s own limits are in Settings → Limits & quotas, and the minutes each build used are on the Deployments tab.

Next steps#