RustREADME
<p align="center">
<img src="dashboard/public/assets/logo-mark.svg" width="64" height="64" alt="Ployz">
</p>
<h1 align="center">Ployz</h1>
<p align="center">
<strong>Rent a server. Get a cloud.</strong>
<br>
Preview environments on servers you own. One command from a fresh server to https.
</p>
<p align="center">
<a href="https://ployz.dev">Website</a> · <a href="#quick-start">Quick start</a> · <a href="#use-it-with-your-agent">Agents</a> · <a href="#status">Status</a> · <a href="#self-hosting-the-dashboard">Self-host</a>
</p>
Ployz turns Linux servers you rent into a deployment platform. It builds your app, gives it an https address and runs its databases and workers next to it. Every pull request can get its own environment. Start with one server and add more when you need them.
<p align="center"> The workflow of the hosted platforms you like, on servers you rent. <br><br> <img src="docs/readme/platforms.svg" width="560" alt="Logos of Vercel, Railway, Fly.io, Render, Netlify and Heroku"> <br> <sub>Six hosted platforms. Ployz isn't affiliated with any of them.</sub> </p>What's different
- An environment for every pull request. Each preview runs the pull request's code at its own https address. Copy the database service and the preview gets its own empty database, seeded by your setup command. A database you leave shared gives the preview production data. On merge, production gets the code and the preview's setting changes. The Ployz · ready to merge check lists those changes on the pull request first.
- Review before you deploy. Edits from the dashboard, the CLI or an agent wait as a draft. You read the diff, then deploy it.
- The CLI does what the dashboard does. Commands print JSON with
--json. A change that would delete a service, a volume or a domain stops until a person approves it. An agent can't approve it. - One private network across your servers. Add a server with
ployz server add. Your