Deployment + Hosting: Amazon ElasticBeanstalk, Google App Engine, Azure App Service, Heroku

Deployment Tool: Buddy https://buddy.works

Hosting: Amazon EC2, Digital Ocean https://www.digitalocean.com/ , Vultr https://www.vultr.com/ , Azure VM, Google Compute Engine

defined over half a decade ago and it is still up to date. I think many IT organizations should seriously think about it

  half a decade ago

Did you mean half a century?

It's been seven years. how much has changed?

what about

Matrix, Avatar, Inception

Docker is the best thing since sliced bread! VM is much more resource and time consuming.

# We switched our dev/stage env to containers 2 year ago.

# We have made our own standalone app in Docker style. Once again - Easy as pie.

if you are a developer you should add Docker + Docker Compose to you working tools.

We moved over to Docker at the development process some time ago and it really speed up our work.

what gives you more than docker-compose itself? with docker-compose and docker swarm I can easily add services there, configure the application environment and scale it.

seems interesting but please enumerate things I can do that are not delivered by docker compose and docker swarm.

A main advantage of Flynn over using docker-compose is that Flynn is more aware of how to run applications out-of-the-box, rather than just running containers which the user has to fully configure.

For example, Flynn comes with PostgreSQL, MariaDB and MongoDB appliances which are deployed in a highly available, fault tolerant configuration with sane defaults: https://flynn.io/docs/databases.

Through the use of buildpacks, it is also straight forward to deploy applications written in many popular languages and frameworks without being intimately acquainted with how to containerise those types of applications (e.g deploying a Ruby on Rails app on JRuby: https://flynn.io/docs/languages/ruby).

You also get things like full cluster backups (including all your data), simple git / docker / tarball based deployments, log aggregation, release rollbacks, domain / path based routing, service discovery, and many more!

Both this and other PaaSes remove a lot of the plumbing. Also, the target audience is different. PaaSes offer self-servixe for end users: for instance starting a new database on demand through the user interface. You can achieve much of this with Docker Compose, but your users can't.

The Docker-PaaS movement reminds me of content-management systems in the early 2000s. Everyone (myself included) thought it'd be great to spend loads of engineering effort reinventing the wheel, instead of delivering business value.

Docker is the best thing since sliced bread!

From their latest newsletters it appears that they intensified cooperation with MS. Hope it does a good turn!

I'd love to see MS's efforts on the linux subsystem bake to a point where Window's container system can support linux containers, which will bring a MUCH more rich ecosystem of possibilities.

there are pros and cons in every solution.

with openoffice barriers between team members are torn down, but it is harder to concentrate, as Joel said.

when you work from home it is easier to concentrate (one condition: you are alone in home), but there are much bigger problems in communication beetween project members.

I have the impression that the approach to this subject comes full circle.

I think you can not find the best solution for all.

Great idea!

I'm sure that GitHub community will help to make it even better

https://github.com/beweinreich/mlooper

The logic made me laugh :)

    def random_reply
      reply = Reply.order("RAND()").first.content

      # if the conversation is getting long, start injecting hipster sentences to the end...
      if self.conversation.emails.count > 10
        reply << " #{Faker::Hipster.sentence}"
      end
      return reply
    end

P.S.: It's a simple Rails app

The author gave the link in the article https://github.com/beweinreich/mlooper.

Thanks for it.

Mlooper?