Last updated: 2026-08-23
vps_deploy is created and maintained by Rafael Egli. Copyright is held by e9li GmbH (Switzerland). The project is open source so you can read it, run it, and adapt it.
If this policy changes, the date above is updated. Git history is the record of what applied before.
How to participate
Open an issue. That is the way to suggest a feature, report a bug, or ask a question. Rafael reads every issue and decides what to implement. There is no obligation that a request will be accepted or scheduled.
Use the GitHub mirror:
- Issues: https://github.com/e9li/vps_deploy/issues
- Canonical source: https://git.e9li.com/e9li/vps_deploy
Please do not send pull requests or patches. The GitHub repository is a read-only mirror for browsing and issues. We will close PRs without merging them. If you have a concrete idea, describe it in an issue; if it is taken up, Rafael implements it.
A useful issue
Include as much of this as you can:
- What you expected, and what happened instead
- Steps to reproduce
vps_deployversion (mix deps/ git ref) and Elixir/OTP on the deploy machine and on the VPS- Your OS (local and server)
- The
:vps_deployconfig fromconfig/config.exs(redact hosts, users, and secrets) - The
mix deploy/mix deploy.setupoutput - For a failed start:
sudo systemctl status <service>and recentjournalctl -u <service>
One topic per issue. Search existing issues first.
Security
Do not file a public issue with a working exploit. Open a GitHub issue that describes the impact only (no PoC), or contact Rafael via e9li GmbH, and wait for a reply before publishing details.
License and liability
vps_deploy is released under the MIT License. See LICENSE.md.
The software is provided as is, without warranty of any kind. Rafael Egli and e9li GmbH are not responsible for damage, data loss, downtime, or other problems that arise from installing, configuring, or using vps_deploy. You use it at your own risk.
Forks are allowed under the MIT terms. A fork is not an official e9li product.