The Deis project is psyched to announce our v0.2.0 release. We've added support for DigitalOcean Cloud, improved our Installation docs, updated Chef, and fixed many issues found by the Deis community.
Deis is a Django/Celery API server, Python CLI and set of Chef cookbooks that combine to provide a Heroku-inspired application platform for public and private clouds. Your PaaS. Your Rules.
deis opentext output
git push deis masterbug with PHP buildpack
deis logssometimes returning 404s
deis createand explicit --id flag
We want to thank the following Deis community members for creating GitHub issues, providing support to others, and working on various Deis branches:
deis nodes:scale--seemed nearly impossible, but Tom found a way. This will land in master soon and enable testing and development on Deis without any cloud provider charges.
Deis currently uses Docker as a LXC wrapper for running Heroku Buildpack slugs that are bind-mounted into Buildstep images. As soon as the Docker Private Registry code stabilizes, we will be adding a new
git push build process that creates and distributes images via
Dockerfile and a private registry hosted on the controller.
Both the controller and formation proxies require SSL configuration. Right now controller sessions are just HTTP with cookies and passwords sent in the clear! We've also glossed over some pretty important security features in an effort to get Deis into developers hands. For example, we need to implement iptables host-level firewalls, improve security group default rules, use Chef recipes to harden systems, etc. If you find any other security holes, please open a GitHub issue and tag it "Security".
We do not currently monitor nodes or container health -- though we have infrastructure in place to do it.
We need to make it as easy for ops folks to publish a set of reusable backing services (databases, queues, storage, etc) and allow developers to attach those services to applications. This will be done in a loosely coupled way, following Twelve Factor best practices.
You can learn about other ways to get involved on our website.
Follow me on Twitter @