ab8eb5a727
Previously a crashed container would stay down, regardless of exit status. In some cases, it may be useful to restart the container. For example, an application may not be correctly implementing their error handling, or the crash may be caused by a transient error. By setting the restart policy to `on-failure:N` - where N is a number of max restarts - we can help developers guard against crashing applications. Note that this is not a replacement for proper error handling, nor does this include notifications to a developer when a container is restarted. Those patterns should be implemented application side, or via a feature request to docker. The value is configurable at the app-level by setting DOKKU_RESTART_LIMIT to a number. By default, containers will be restarted a max of 10 times. If a container crashes during the check-deploy plugin trigger, then the deploy will be marked as a failure. Closes #216 Closes #398 Closes #1327
Dokku 
Docker powered mini-Heroku. The smallest PaaS implementation you've ever seen. Sponsored by our friends at Deis.
Requirements
- A fresh VM running Ubuntu
14.04 x64
Installing
To install the latest stable release, you can run the following commands as a user that has access to sudo:
wget https://raw.github.com/progrium/dokku/v0.3.26/bootstrap.sh
sudo DOKKU_TAG=v0.3.26 bash bootstrap.sh
Upgrading
View the docs for upgrading from an older version of Dokku.
Documentation
Full documentation - including advanced installation docs - are available online at docs
Support
You can use Github Issues, check Troubleshooting in the documentation, or join us on freenode in #dokku
Contribution
After checking Github Issues, the Troubleshooting Guide or having a chat with us on freenode in #dokku, feel free to fork and create a Pull Request.
While we may not merge your PR as is, they serve to start conversations and improve the general dokku experience for all users.
Sponsors
Dokku is currently sponsored by the enterprise grade, multi-host PaaS project Deis.
License
MIT