Let me preface this by saying that I'm a huge fan of Deis and the team. I went through the process of setting up a cluster a few months ago and they were incredibly helpful and responsive in IRC. Highly suggest, would love to work with the project again.<p>That being said, I'm a little confused as to how Deis can be considered production ready when the underlying infrastructure (Etcd and Fleet from CoreOS) aren't. Both are making great progress, and I wouldn't worry too much about using them directly, but "production ready" abstractions on top of something maybe-not-so-production-ready makes me cringe a tiny bit.<p><a href="https://github.com/coreos/etcd/blob/master/Documentation/production-ready.md" rel="nofollow">https://github.com/coreos/etcd/blob/master/Documentation/pro...</a>
After reading a bit through it and i am wondering what the limitations are. I am a bit "scared" that deis talks about heroku so much and about HTTP.
From the documentation it seems that the containers can ONLY use one port and that must be HTTP. Is that right?
Also, the external storage is mentioned everywhere but not exactly what it is. I have read that Postgres is a database for the applications. What about plain files? Can my apps persist files on the external storage?<p>If this is only about pushing the next Go-based Todo web app to some servers, i'm disappointed... :(<p>Usecase: Is it possible to run mail servers on it?
Can somebody explain what the use-case for this is? The site says it is a "PaaS that makes it easy to deploy and manage applications on your own servers".<p>Most apps I've been making follow a similar recipe: run single ubuntu instance on digitalocean, use nginx for http to serve static content for single page app (ex. angular project), and nginx proxy to gunicorn to serve a python flask API that stores and retrieves data to/from mongodb.<p>Where in that picture would something like Deis fit in? Or is this not for me?
"Deis must make it simple for ops folks to publish a set of reusable backing services (databases, queues, storage, etc.) and to allow developers to attach those services to applications."<p>What are some projects focused on implementing these *-as-a-service components in a cloud-agnostic manner? Rancher is one that came up earlier today on HN.<p>[0] <a href="http://www.ibuildthecloud.com/blog/2014/11/11/announcing-rancher-dot-io/" rel="nofollow">http://www.ibuildthecloud.com/blog/2014/11/11/announcing-ran...</a>
We've been using Dokku for a month or so for deploys on a project and aside from a few initial minor bumps it's made the deploying as simple as Heroku for me and taken a ton of the pain out of devops.<p>Deis/Dokku are great tools for developers looking to abstract away a lot of the pain of getting an app into production.
Congratulations, @gabrtv. And thanks for all the hard work. I've been following this work weekly since we spoke over a hangout in the latter OpsDemand days. I've tried out a couple beta versions, but I can't wait to try out the real deal here at KnowledgeTree.
Correct me if I'm wrong.<p>Deis = heroku-like interface on top of your own private cloud which must be running CoreOS and certain other things like Ceph distributed filesystem, but can be set to run on a variety of third party commercial cloud providers' infrastructure.<p>So basically, if you only ever want to use these features, and you are happy with a heroku-like interface to your infrastructure, Deis is useful.<p>OTOH, if you might want to run a non-Linux node, a specific filesystem or node-local configuration for performance, security or other purposes, or have infrastructure that is not feasibly manageable with a manual process, Deis is not currently useful.<p>That said, neither are most of the latest-gen infrastructure solutions.
I'm interested in hearing pros/cons of Deis vs Kubernetes.<p>The primary disadvantage I can see for Deis is that it can only deploy single Docker containers (vs Kubernetes pods). Given the Heroku-style setup it makes sense, but it is limiting for more complex applications.<p>On the other hand, the simplicity of Deis is attractive. I kind of <i>wish</i> I could use it, but I feel like it just isn't feasible for a full suite of microservices + dependencies.<p>Regardless, congrats on 1.0!
I'm still not grasping the concept of Docker and such...<p>Can I use Deis (albeit in a much smaller scale) to quickly spin up lightweight VM-ish entitys for prototyping new webapps/backends (i have an unused box at home), or am I coming at this from the wrong end :)
(Link to a _good_ explanation of Docker, preferably a video ;), would be gratefully appreciated)
I already use CoreOS/etcd/fleet to manage a cluster of apps and services. What does Deis do that I can't already? Does it have solid automation for service discovery and the like? I want to be able to quickly add and remove nodes depending on demand. Does Deis make this easy?
I'm a big fan of Linode but I see Linode isn't amongst the supported cloud providers. Is there some fundamental issue here or is it just lack of time / resources to develop support?
I'm really struggling to understand what this is. I've looked at it a few times and never really get a good grip on what it is.<p>Also, how does it fit in with Ansible?
are there any deis with ruby or rails application tutorials? I didn't see any, but for getting people from heroku, it would be great to see some tutorials so people can easily migrate.<p>on the minimum cluster of 3 nodes with 2 gb each, what is the minimum amount of apps that could be run?