Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
To deploy a full-stack app with Peon, connect a Linux VPS over SSH, choose a deployment type that matches your app, configure its environment and storage, then route a domain through a gateway for HTTPS. Peon manages deployment and service orchestration; you provide the server and the application-specific configuration. With Peon Cloud, the control plane is hosted by Peon while your app and database still run on your VPS.
Choose where to run Peon’s control plane
Peon’s control plane provides the dashboard and deployment coordination. It is separate from the server that runs your application.
| Option | Where the control plane runs | What remains on your VPS | Documented cost or requirements |
|---|---|---|---|
| Peon Cloud | Hosted by Peon | Your application and database workloads | Peon lists $3 per project monthly or $30 yearly for Cloud; check its current pricing documentation before signing up. |
| Self-hosted Peon | On infrastructure you manage | Your application and database workloads; the control plane also runs on infrastructure you manage | The control plane is free to self-host. Its documented prerequisites include Node.js 20+, pnpm, PostgreSQL, and a production HTTPS domain; see Peon’s self-hosting guide. |
Choose Cloud if you want Peon to host the dashboard and workers. Self-hosting suits operators who want the control plane on their own network or want its dashboard database under their control. Neither option supplies the VPS for your app.
Prepare the VPS before connecting it
Peon documents the following as server guidance, not a universal capacity guarantee. Size the host for your own app, traffic, builds, and database workload.
#1 Best Overall
- Use a 64-bit Linux server with SSH access.
- Have root access or a user with sudo privileges for first-time Docker installation.
- Peon lists approximately 1 GB of RAM as a minimum and recommends 4 GB or more for a host running multiple services.
- For public HTTP and HTTPS routing, allow inbound traffic on ports 80 and 443.
See Peon’s server requirements and troubleshooting documentation for current details. Make sure your firewall and any provider-level network rules permit the connections you need.
Connect the server to Peon over SSH
- In Peon’s workspace settings, create an SSH key.
- Add a server using its IP address or hostname, SSH port, login user, and the key you created.
- Run Peon’s connection or validation flow. It checks access and handles Docker setup where required.
- Confirm the server agent is live; Peon uses it to provide operational metrics.
If validation fails, check the hostname or IP, SSH port reachability, key selection, login username, and sudo access. The connected account must be able to complete the Docker setup Peon requires. Follow the current server connection instructions for the product’s exact screens.
Choose a deployment shape for your app
Peon supports several ways to deploy workloads. Select based on what your repository contains and how its components need to run; a full-stack app does not have to use one fixed layout.
| Deployment type | Use it when | What you configure |
|---|---|---|
| Git application | You want Peon to retrieve source and build the app. | Connect through a GitHub App, public repository, or deploy key, then select a supported build option such as Nixpacks, Railpack, Dockerfile, or Static. |
| Docker image | You already build and publish an image. | Choose the image and version, then configure its listening port, environment, domains, and storage as needed. |
| Compose stack | Several containers are described and managed together. | Supply the Compose configuration and check how its services, networks, volumes, and update behavior work with your app. |
| Static site | The deployable result is built files rather than a long-running application process. | Configure the static output and public domain. |
| Database service | You want to provision a supported database service through Peon. | Choose a supported database type and set its credentials and persistent storage deliberately. |
For a common architecture, the frontend may be a static site or an app service, the API runs as an app service, and the database runs as a separate service. That is an architectural choice: the repository’s runtime and deployment requirements determine whether components belong in separate services or a Compose stack. Peon’s current service documentation describes supported types and setup screens.
If you deploy a prebuilt Docker image
Configure the container’s listening port so Peon’s reverse proxy can reach the process. Add the public hostname in the service’s Domains settings and leave the gateway enabled if Peon is handling public routing. The Docker-image guide covers image, environment, and named-volume configuration. Pin a specific image version when you need repeatable deployments; a floating latest tag can point to different builds over time.
Configure secrets, persistent data, and health checks
Set application environment variables
Peon says it injects encrypted environment variables during deployment. The names and values are app-specific: use the application’s own configuration documentation to determine what it expects. Keep credentials and other secrets in Peon’s environment configuration rather than committing them to source control.
Rank #4
Store data outside replaceable containers
Container replacement is a normal part of deployment, so do not assume files written only inside a container will survive an update. Configure persistent storage or named volumes for data that must remain, including database files where the selected service requires them. Use the Docker-image storage documentation for the relevant volume settings.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Make health checks represent readiness
For eligible rolling updates, Peon starts a new container and switches traffic after its health check passes; the previous image can be retained for rollback. Configure the check to reflect whether the app is actually ready to serve requests, not merely whether a process has started. This behavior is not a blanket zero-downtime guarantee: Compose and some database update paths may be less gradual. Peon describes deployment behavior in its overview documentation.
Best Value
- Ultimate Freshness & Flavor: The condiment caddy’s lower compartment ingeniously holds ice cubes or crushed ice, actively keeping vegetables, sauces, or fruits succulent and fresh for hours. Each top compartment features a removable lid for easy access
- Safe, Stylish & Complete with Accessories: Crafted from sturdy, BPA-free PET plastic, our condiment organizer offers food safety and elegant aesthetics. The set includes 2 metal clips and 5 metal spoons for grabbing and scooping fruits, vegetables, and sauces. The crystal-clear design provides a seamless view of contents, perfect for beautifully presenting fruits, salads, or any treats. (Note: Avoid direct contact with hot food.)
- Modular Capacity for Every Need: Each individual lidded compartment 5.7"(14.4cm) × 3.8"(9.7cm) × 2.4"(6.2cm) holds 2.5 cups, ideal for single servings. The complete set includes 5 removable compartments fitting perfectly into the main tray 15.7"(40.6cm) × 6.2"(15.8cm) × 5.1"(13cm), offering ample total capacity
- Effortless Cleaning & Clear View: Constructed from transparent plastic, this garnish tray offers a clear view of stored food and ice. After use, it conveniently rinses clean with water. For thorough hygiene and longevity, HAND WASHING is highly recommended. (Important: Not dishwasher safe.)
- Versatility for Every Celebration: This fruit tray transforms into your go-to server for family gatherings, picnics, BBQs, and indoor/outdoor parties! Use it as a convenient hot dog/pizza toppings station, stylish bar garnish caddy, vegetable/fruit tray, or a complete taco bar serving set
Attach a domain and enable HTTPS
- Point the domain’s DNS records to the VPS address.
- Add the hostname to the deployed service using Peon’s domain configuration.
- Enable Peon’s managed gateway if it will handle reverse proxying and HTTPS. Peon documents Traefik, Caddy, and None as gateway choices; None means you need another routing solution.
- Allow inbound ports 80 and 443 through the server firewall and provider network rules.
- Wait for DNS to resolve to the VPS, then verify that the domain serves the app over HTTPS.
If routing or certificate setup fails, check DNS resolution, gateway status, firewall rules, and whether another service already occupies ports 80 or 443. Peon identifies a disabled gateway and busy HTTP(S) ports among common proxy and HTTPS problems in its server troubleshooting guide.
Deploy, monitor, and recover
A deployment queues work for the target server: Peon pulls the selected commit or image, builds from source when required, injects configured variables, and starts containers on the network shared with the gateway. Use the current Peon interface to review deployment status and logs when a build or service fails; consult the product’s deployment documentation for current screen names.
When an eligible service has a bad release, use Peon’s rollback capability to return to a retained prior image. If the deployment type does not use the documented rolling-update path, check its service-specific update behavior before relying on image rollback.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
