piku, inspired by dokku, allows you do git push deployments to your own servers, no matter how small they are.

Installing Using/Features Managing and Monitoring Examples Web App Tutorial

Demo

Workflow

piku supports a Heroku-like workflow:

• Create a git SSH remote pointing to your piku server with the app name as repo name: git remote add piku piku@yourserver:appname.
• Push your code: git push piku master (or if you want to push a different branch than the current one use git push piku release-branch-name).
• piku determines the runtime and installs the dependencies for your app (building whatever's required).
• It then looks at a Procfile and starts matching worker processes.
• You can optionally also specify a release worker which is run once when the app is deployed.
• You can then remotely change application settings (config:set) or scale up/down worker processes (ps:scale).
• You can also bake application and nginx settings into an ENV configuration file.

You can also deploy a gh-pages style static site using a static worker type, with the root path as the argument, and run a release task to do some processing on the server after git push.

Project Activity

piku is considered STABLE. It is actively maintained, but "actively" here means the feature set is pretty much done, so it is only updated when new language runtimes are added or reproducible bugs crop up.

It currently requires Python 3.7 or above, since even though 3.8+ is now the baseline Python 3 version in Ubuntu LTS 20.04 and Debian 11 has already moved on to 3.9, there are no substantial differences between those versions.

Deprecation Notices

Since most of its users run it on LTS distributions, there is no rush to introduce disruption. The current plan is to throw up a warning for older runtimes and do regression testing for 3.7-3.12 (replacing the current bracket of tests from 3.5 to 3.8), and make sure we also cover Ubuntu 22.04, Debian 11 and Fedora 37+.