4 ms·
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 do
by buster 12y ago
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?
If this is only about pushing the next Go-based Todo web app to some servers, i'm disappointed... :(
Usecase: Is it possible to run mail servers on it?
- HorizonXP 12y agoI don't know about Deis, but I'm using CoreOS, fleet, etcd, and docker for HTTP, mail, and other network protocols. It's been an amazing combo.
- barrybob 12y agoYes the Deis router only supports HTTP at the moment, sadly no TCP. I hope/think it's something they are going to work on after v1 is stable. It also has no persistent storage; the database you are referring to is for the deis application itself. You could use it, but it's not wise. Realistically you should use something similar to Amazon RDS or Rackspace cloud databases, as each deis node is ephemeral. It's still really early days, I have seen a few mentions on their github page that outlines the features you're wanting, and I can't wait for them myself.
- bacongobbler 12y agoyes, tcp support in the router is something we'd like to work on but is not there yet for v1.0.
- barrybob 12y agoGood to hear! Any plans for supporting databases in the future? That's the main deal breaker for me at the moment. Keep up the awesome work.