Getting Started

Configuration

Configure compute bounds, custom ports, and service specs.

Dequel provides fine-grained control over container resources and network routing to ensure optimal application performance and stability.

Resource Limits

Configure boundary limits under the Settings layout to avoid cluster resource starvation or application OOM (Out Of Memory) crashes:

CPU Limit (cores): The maximum amount of CPU shares a container replica can consume. Specifying 1.0 permits a full single core.
Memory Limit (MB): The boundary RAM limit allocated. If a container exceeds this, it is automatically terminated with an OOM error code and restarted. Recommended default: 512MB.

Port Configurations

Dequel’s edge router (Caddy) uses reverse proxy routing to map incoming HTTP request traffic to your container.

⚠️ Crucial Note: Internal Ports

Your application inside the container must bind to the environment-injected PORT variable. Hardcoding listen ports to 3000 or 8080 without reading the environment variable will result in a 502 Bad Gateway error, as Caddy's dynamic routing target won't match.

Example: Express server

server.js

const express = require('express');
const app = express();
// ALWAYS read from process.env.PORT
const PORT = process.env.PORT || 3000;
app.get(’/’, (req, res) => {
res.send(‘Hello from Dequel!’);
});
app.listen(PORT, ‘0.0.0.0’, () => {
console.log(Server listening on port ${PORT});
});

Next: Deployments