ddollar's comments

We are considering other vendors but currently focused on AWS. What vendors would you like to see?

Currently we only offer Convox the open-source platform :) In the future we are considering paid support and other monetization strategies but the base platform itself will always be open-source and available for you to do with as you please.

Yes, we have people using this in production, including ourselves! Most of the scale right now is on the small-to-moderate end but once your application is up and running you're really only limited by how much AWS you want to pay for :)

Empire is awesome, we think it's a great project. We have been swapping notes with the folks working on it.

The primary difference is that Convox is backed by a company for which this is our product and has a full-time team dedicated to it.

Yes, there is a business behind Convox. The founders are all ex-Heroku engineers and have we all have a great deal of experience building this type of tooling and automation.

For now we are focused on building a great open-source platform.

ECS is working out great for us. We host all of our own internal infrastructure on Convox and have been very happy.

The minimum per-application cost would be for an ELB. Counting the slice of runtime cluster needed to run it I'd estimate around $20-25 per app as a minimum.

We're strongly considering other clouds but are focused on AWS for the moment.

Unless it has changed since I last look Dokku only runs on a single server.

The other major difference is that software like Dokku is trying to run anywhere. Because we are only trying to run on AWS we do not need to build custom schedulers, load balancers, routers, etc. We believe this will reduce your operational costs over time.

Absolutely! You can decide not to use a front-end load balancer. We have one user using Convox to spin up large worker pools on AWS.

We also have plans on our roadmap to integrate with internal (inside the VPC only) ELBs for internal APIs and things of that nature.

You're quite welcome! All three of the Convox founders are huge proponents of open source. We've already seen the benefit from this as a user has mapped out the missing pieces to host HIPAA-compliant applications on Convox and has already started making the necessary changes.

https://github.com/convox/kernel/issues/92

It is similar to Deis in goals but it differs substantially in implementation. Because Convox runs on AWS we can rely on stable and scalable services only available on that platform such as ELB and DynamoDB. Deis uses its own internal Postgres and implements a custom load balancer, scheduler, etc. We believe using the hosted services will help you keep your operational costs down over time.

Hello! I'm part of the Convox core team and happy to answer any questions.

Convox is an app deployment platform that you can install into your own AWS account. It uses ECS, ELB, Kinesis, and many other great AWS services under the hood but automates it all away to give you a deployment experience even easier than Heroku.

Convox uses Docker under the hood so if you want to customize anything (distro, dependencies, etc) you can simply add a Dockerfile to your project.

Convox is entirely open source. Check it out at https://github.com/convox

To get started with our installer go to: http://docs.convox.com/docs/getting-started-with-convox

> The selling point behind these devices is convenience, but at the cost of security. I don't think I need to explain to HN why an always-on, internet connected voice recording device is something to keep out of your house.

Do you have any computers in your house? A TV made in the last few years? A smartphone?

I have not found myself needing to change those things very often once I have created the initial Dockerfile.

If you've got the time I'd love to hear more about your workflow at [email protected]

I'm really excited about the idea of groups that may be coming to Docker. It seems like a great primitive around which to build tools like fig and tug and perhaps other tools to orchestrate production.

https://www.youtube.com/watch?v=YuSq6bXHnOI

Sorry about that! I'm trying to get the docs into shape as fast as possible.

If a line starts with "docker/" the rest is assumed to be a docker image tag.

Thank you for the kind words and the clarifications Mitchell :)

Tug is a simple tool that I wrote to scratch a personal itch around working with dockerized applications and trying to optimize for startup speed and writing as absolutely little configuration as possible.

I'm hoping to get a few other people to try it out and let me know if it works for them and if it's useful, especially given the existence of so many other tools of this nature.

Awesome :) I think then that the primary difference with Tug is that it can work in a "hybrid" virtualized/local mode if you haven't yet written a Dockerfile/Vagrantfile/other for your app. Tug can start by simply spawning dependencies like Postgres and Redis and let you incrementally move towards a Dockerfile for your app.

Nice :) I believe Vagrant also now has built-in support for Docker which is very useful for starting up ancillary services that your app needs: https://docs.vagrantup.com/v2/provisioning/docker.html

I quite like Vagrant myself but my primary complaint is that I seem to spend a lot of time waiting for VMs to start up and run a lot of bootstrap code.

Tug primarily differs from fig in two ways:

* Less verbose configuration, tries to assume sensible defaults

* Works with apps that do not yet themselves have a Dockerfile