|
|
|
|
|
|
by thedevopsguy
3921 days ago
|
|
|
Hi Ctex, It's neat that beluga is written predominantly in bash but it's also difficult to see what Beluga actually does. Right now it looks like it sets up an environment for a docker compose app to run. Similar to docker machine but also solvable by tools like ansible, salt or python fabric. Kubernetes and Mesos are solving different problems. They manage and orchestrate services and add ons may also help with repository management. My view may come from a lack of understanding of the tool's primary use case. Deeply interested in new developments in the docker ecosystem. Could you please update your current documentation with a few examples. |
|
|
The whole goal of beluga is to take your docker-compose project from your machine to a remote host and have it running.
It's meant to be used with the existing docker-machine & docker-compose tools and shouldn't interfere with any internal docker apis.
Beluga was originally written in bash as we didn't want to impose runtime dependencies. Bash is usually pretty much available everywhere expect bsd.
It also accounts the fact that if you have to deploy to multiple machines you won't have to rebuild your project everywhere as it can push and pull the images from either dockerhub or your own self hosted docker registry (either https://github.com/docker/docker-registry or https://github.com/docker/distribution).
Here's a link to a sample node.js project that is deployed with beluga. https://github.com/cortexmedia/Beluga-SampleProject-Nodejs
It's pretty much a standard docker-machine & docker-compose project but with an additonal file.