Show HN: Hosted Docker-as-a-Service on SSDs for $5 • Hacker News Board

Re: Show HN: Hosted Docker-as-a-Service on SSDs for $5

#131

Post by nailer » Fri, Nov 08, 2013, 2:12 PM UTC

edbyrne wrote: post #18

Angostura wrote: post #15

I love the fact that you keep trying to define your own vocubulary 'Deck' etc, but always have to explain it. Best to stick with the more eaily understood term, rather than invent your own, I think. Unless you're going to try and trademark them all.

Thanks - we discussed that a lot - we were trying to make a simple 3 steps process. If we get a lot of feedback that it's confusing we'll ditch it.

I'm in a similar problem space to you. After a year of defining my own 'simpler' terminology, decided to abandon it in favour of being consistent with the more popular albeit complex terminology.

I hope that saves you some time.

Re: Show HN: Hosted Docker-as-a-Service on SSDs for $5

#132

Post by mscarborough » Fri, Nov 08, 2013, 3:08 PM UTC

gizzlon wrote: post #126

peteforde wrote: post #66

Earlier quoted context omitted.

Heroku created almost as many new terms as Tolkien, and they seem to have made out just fine.

Looked at Heruko once, but all the custom lingo really put me off it.. But, of course your point about them being successful stands

It's worth a shot if they fit your use case. Once you get past the ninja-speak of choosing size and database, it's really simple.

For rake/rails apps at least, you just run `heroku run 'command'` and you're done.

Re: Show HN: Hosted Docker-as-a-Service on SSDs for $5

#133

Post by shykes » Fri, Nov 08, 2013, 8:37 PM UTC

StavrosK wrote: post #130

shykes wrote: post #91

Earlier quoted context omitted.

There is a new feature of Docker called Links which allows you to organize your stack in multiple containers and "link" them together so they can discover and connect to each other. There's a great explanation here: http://blog.docker.io/2013/10/docker-0-6-5-links-container-n...

I tried to deploy a Django application with Docker a few weeks ago (using a single image with supervisord), only to discover that, during "docker build", I needed the database already running (so Django could create its database), which was pretty much impossible using a single Docker image and a Dockerfile. With the new Links functionality, this is much easier, but are you planning to ever have the ability to use a…

> are you planning to ever have the ability to use a single Dockerfile to deploy an application which may contain multiple images (with links between them)?

Yes, definitely :)