Study how pre-Kubernetes container deployment platforms handled push-to-deploy workflows
Understand the Docker-plus-CoreOS era architecture for building your own internal platform
Reference the cluster scheduler and routing layer design when evaluating modern PaaS alternatives
Trace the design decisions that led to the Kubernetes-based Deis Workflow successor
Retired and unsupported since 2017, do not use for new projects, repository exists for historical study only.
Deis v1 is an archived open-source platform that let you run your own app-hosting service on your own servers. Think of it as a private version of Heroku: you give it a server or a cluster of servers, and it handles the work of deploying, scaling, and managing your applications. The project was built on Docker (a system for packaging applications into self-contained units called containers) and CoreOS (a minimal Linux operating system designed for running containers at scale). The command-line workflow was modeled after Heroku, so developers who already knew that style of deployment could adapt without learning an entirely new mental model. The appeal was control over your own infrastructure. Rather than paying a cloud provider to host your apps on their terms, you could run the same kind of push-to-deploy workflow on servers you owned or rented. Deis v1 could be installed on public clouds such as AWS or Google Cloud, on private servers, on bare metal hardware, or even on a local development machine using Vagrant for testing purposes. Deis v1 is no longer maintained. The project was officially retired in 2017, and the repository now exists only as a historical reference. The README makes this plain: the code is unsupported. Active development moved to a successor called Deis Workflow, which the team rebuilt on top of Kubernetes instead of CoreOS. The README itself links to that project as the replacement. If you are studying the history of container-based deployment platforms, this codebase shows how teams approached the problem in the Docker-plus-CoreOS era, before Kubernetes became the default approach. For any new project, you would not want to build on this archived code.
← deis on gitmyhub — every repo by this author, as a profile.
Verify against the repo before relying on details.