Your own servers
Our cloud runs Pushleft, and your apps and databases run on servers you own. One command on a Debian or Ubuntu server installs the agent and adds the server to your organization. Only your organization’s work runs on it.
Requirements
- A Debian or Ubuntu server on x86_64, with systemd. Use a fresh server: the install sets up Docker with user-namespace remapping, and containers that already run on the host are then hidden from Docker.
- Root access, or
sudo. - More than 1 GiB of memory. A build server needs room for one build.
- A data disk, or free disk space. Give an empty disk (for example
/dev/sdb) and the install formats it as XFS. Without a disk, the install makes a 50 GiB file, and it needs 10 GiB of free space more than that. - Outbound HTTPS to
console.pushleft.dev, and togateway.pushleft.devon ports 8443, 8444 and 8445. The clock must sync with NTP. - For a server that runs apps: inbound ports 80 and 443 from the internet, or the tunnel option (servers behind NAT).
- An owner or admin role in the organization.
Your tier sets how many servers you can add: 2 for a new organization, 10 for standard and 50 for trusted. Ask support for a higher limit.
Add a server
A new organization gets the same steps in the console’s setup, under Your own servers.
-
Open Nodes in the console.
-
Under Add a node, choose what the server runs: applications, databases, applications and databases, or builds.
-
Type the region. Use a region that your
.pl.yamllists underproduction.regions, for examplefsn1. -
Optional: type the data disk, for example
/dev/sdb. -
Click Get install command.
-
Copy the command and run it on the server within 15 minutes:
s=$(curl -fsSL -H 'x-pushleft-install: <secret>' https://console.pushleft.dev/v1/node-install/<org>) && printf '%s\n' "$s" | sudo bash
The command works once. It holds a one-time secret, so do not share it.
The CLI does the same:
pl nodes enroll --pool application --region fsn1
pl nodes enroll --pool database --region fsn1 --data-device /dev/sdb
Add --out node.sh to also save the full script. Run it later with ssh root@<host> 'bash -s' < node.sh, within the same 15 minutes.
Install progress
The install takes a few minutes. The Nodes page shows each step as it finishes: Download, Packages, Clock, Docker, Data disk, Agent, Enrol and Start. The install does this on the server:
- Installs the packages it needs, Docker included.
- Turns on NTP and waits until the clock is in sync.
- Sets up Docker with user-namespace remapping and the firewall.
- Prepares the data disk at
/var/lib/pushleft/dataas XFS with quotas. - Downloads the signed agent and checks its signature.
- Enrolls the agent with a client certificate, and starts it.
After the install, the agent reports the server’s CPU, memory and disk. Pushleft then admits the server, and new work can go to it. Until then the status says why, for example “connecting” or “needs over 1 GiB memory”.
pl nodes list shows the same status. The install also writes its output to /var/log/pushleft-install.log on the server.
Fix a failed install
When a step fails, the Nodes page marks it in red. It shows the failed command and the last lines of its output.
- Read the error, and fix the cause on the server. For example, the install never formats a disk with a partition table. Wipe the disk or choose an empty one.
- Click New command on the node, or run
pl nodes command <id>. - Run the new command on the server.
New command also shows when a command expired before you ran it, and when the install sent no progress for 5 minutes. The old command then stops working. You can run the install again on the same server.
Servers behind NAT
A server with no public address can still serve your apps. Select No public address when you add it, or use pl nodes enroll --tunnel. This option is for servers that run applications.
Traffic to your apps then goes through a Cloudflare tunnel in Pushleft’s Cloudflare account. The agent on your server runs the tunnel connector, so the server needs no inbound port. Cloudflare ends TLS for these hostnames, so Cloudflare sees that traffic. A hostname moves to the tunnel after the connector is connected.
Work placement
- Pushleft places only your organization’s applications, databases and volumes on your servers.
- On the plan for your own servers, your work runs only on your servers. Pushleft places it in the regions that your
.pl.yamllists. - On the Cloud plan, you choose where new work runs. Set it for production and for previews, under Work placement on the Nodes page or with
pl nodes placement:
| Setting | New work goes to |
|---|---|
own_first (default) | Your servers. Pushleft’s servers only when none of yours has room. |
own_only | Your servers only. With no room, the deployment waits. |
pushleft | Pushleft’s servers only. |
- Only work on Pushleft’s servers costs compute. Work on your servers costs nothing extra.
- A change applies to new placements. Running work and databases stay where they are. To move them, redeploy the environment from scratch (preview region).
- A preview without
preview.regionruns in the regions of your servers, and also infsn1withown_first. A production deployment runs in the regions thatproduction.regionslists. - Builds run on your own build server when you have one in the region. Without one, they run on Pushleft’s shared build servers, and the image goes to the registry.
- The control plane, the console, the registry and the platform DNS run in our cloud.
Data on your server
- Your app containers, their volumes and your databases stay on your server.
- Pushleft takes no daily backups of the databases and volumes on your server. Back up the server yourself.
pl db backup <db>takes a backup on demand, on the server’s own data disk. - Metrics and logs go to Pushleft by default. Clear Send metrics and logs, or use
--no-telemetry, and Pushleft collects none from the server. - Secrets reach the server only for the work that is placed on it.
When Pushleft loses contact with one of your servers, the owners and admins of the organization get an email.
Drain and remove
- Drain the server: Drain on the Nodes page, or
pl nodes drain <id>. No new work goes to it. Running work stays until you move it. - Remove the server: Remove, or
pl nodes remove <id>. Pushleft revokes its certificates.
You can remove a server only when no work is placed on it. Pushleft deletes nothing on the server itself.
Price
The plan for your own servers costs €10 a month. You also pay for the datasets, buckets and registry images that you store with us. The database plan you choose sets the size on your server and adds no cost. Compute and disk on your own servers cost nothing on Pushleft. See usage and budgets.
Related
- Fleet: the full detail of customer-owned nodes, for operators.
- The .pl.yaml manifest: regions and the work that runs on your servers.
- Managed databases: databases, backups and restores.