A Docker Abstraction That Handles Container Security

Re:A Docker Abstraction That Handles Container Security by the_common_man on Tuesday July 25, 2017 @08:53PM (#14853023)

How is this different from heroku?

[ Parent | on HN ]

Re:A Docker Abstraction That Handles Container Security by technologyvault on Friday July 28, 2017 @06:07PM (#14877998)

The main difference is that the Nanobox PaaS is portable, making it what's been termed a "micro-PaaS". You can host with whatever cloud provider (AWS, DigitalOcean, Linode, Google Cloud) you want or set it up on-premise.

Businesses who want to (or have to for compliance reasons) use a different host (e.g. Vultr in Europe or Alibaba Cloud in Asia) can simply create their own adapters and deploy away: https://docs.nanobox.io/providers/create/

[ Parent | on HN ]

Re:A Docker Abstraction That Handles Container Security by tylerflint on Tuesday July 25, 2017 @10:50PM (#14853383)

https://nanobox.io/why-nanobox/nanobox-vs-heroku/

[ Parent | on HN ]

Re:A Docker Abstraction That Handles Container Security by rhizome on Tuesday July 25, 2017 @09:25PM (#14853142)

Well, to begin with, Heroku has a bare minimum of interactive functionality, and this is a containered VM with a fancy cPanel successor. How are they similar?

[ Parent | on HN ]