Browse documentation

Add a server

Register a Linux host, authorize Bundar's SSH key, and install the runtime and proxy needed for deployments.

Bundar connects to your host over SSH. Before adding it, make sure it is reachable from Bundar on the SSH port you intend to use, and that the SSH account can install packages and manage system services. Current automated setup supports Debian or Ubuntu (apt) and CentOS, RHEL, Rocky Linux, or AlmaLinux (dnf); deployment actions use systemd.

Register the host

From your organization, choose Add server. Enter a friendly Server Name, the server's IP address or hostname, its SSH port (22 by default), and the SSH user (root by default). Choose one of the key options:

  • Generate New creates an ED25519 key pair for this connection.
  • Use Existing selects a key already saved for this organization.
  • Enter Your Key accepts the matching public and private key.

When you choose an existing or pasted key, the public key must already be authorized for the SSH account on the host. With a generated key, Bundar shows an automatic setup command and a manual public-key method on the next page.

Connect and prepare it

After Add Server, Bundar opens Get this server ready. Run the displayed one-time automatic setup command on the server to add Bundar's public key and notify Bundar, or add the displayed public key to ~/.ssh/authorized_keys yourself. Treat the tokenized setup command as sensitive; it authorizes this server bootstrap.

Choose Test connection. Once SSH succeeds, install Podman. This setup also installs Git, enables Podman systemd units, and provisions subordinate user-ID ranges used by containers. Install the Web Proxy to run web applications; this sets up Caddy and the proxy network. Firewalld is optional and is not required for application readiness. The page offers individual install buttons and Install all.

Podman is enough for a worker. A web application is considered ready only when the server is online and both Podman and the proxy are running. If setup fails, inspect its progress output on the setup page and retry that step after addressing the host-side error.

Once the server is ready, continue with Add an application. For background and the initial sequence, see Getting started.

Delete a server

Choose Delete Server from server settings or setup. This deletes the server's applications and deployment records in Bundar. Preserve resources is selected by default and leaves remote resources untouched.

Choose Reset Podman for complete remote cleanup. Bundar submits podman --log-level=error system reset --force through systemd-run, removing all containers, images (including build caches), networks, volumes, and Podman storage for the configured SSH user. This includes resources not managed by Bundar; do not choose it if that user runs unrelated workloads. It does not uninstall Podman or remove resources owned by other users. Remote cleanup must succeed before Bundar deletes the server record. This requires a systemd host and permission to create system-level services (normally a root SSH connection); there is no direct-SSH fallback. The service uses runuser to execute Podman as the configured SSH user.

Bundar waits up to 10 minutes for a reset result. Losing SSH or reaching that wait limit does not stop the remote service: the deletion job can reconnect and adopt the same unit on retry. A nonzero exit or Podman error output marks the reset as failed. Failures keep the server and its application and deployment records in Bundar. Deletions queued under the older Delete managed resources option retain their original scope: they remove Bundar containers, networks, volumes, and proxy resources without resetting Podman or removing images.