With Engine 2.1.0, we made it easier to get a project running on your own VPS. But a successful first deploy doesn’t mean the work is done. There’s still the next update, the next redeploy, and everything that goes into keeping it running.
That’s the part we’re making better with PanelAlpha Engine 2.1.1. It’s now available, with a broad range of improvements focused on reliability, security and making everyday self-hosting tasks easier.
Some of the changes we’re especially happy with:
-
Safer redeploys. Engine can now start the new version of the project alongside the running one and checks that it’s working before switching over. If something goes wrong, the previous version stays online.
-
Stronger project isolation. We’ve tightened network access between projects, so one application can’t freely reach another or access parts of the server it shouldn’t.
-
Better server protection. Engine now uses ufw and fail2ban to manage firewall rules and help protect services against repeated failed login attempts.
-
More checks in the background. Engine keeps a closer eye on available disk space, prevents conflicting deployment operations and warns you when stored credentials can’t be read properly.
-
Support for more application setups. We’ve added Procfile workers, release commands, persistent paths, Git deploy keys and private registry authentication.
At the same time, we’re actively bringing Engine closer to full compatibility with the PanelAlpha Control Panel. It’s still a work in progress, but one we’re putting a lot of attention into. So if you’re currently using PanelAlpha together with Engine, please stay on your existing Engine version for now.
As always, we’d love to know how the new version works for you. Try it with your projects, tell us what we’re still missing, or open an issue if you run into something unexpected. And if you’d like to contribute directly, the repo is open!
Take a look at the full changelog and release notes to catch up on everything that’s been happening with Engine.