tsuru / diaats

Docker image as a tsuru service.

tsuru

What is tsuru?

tsuru is an extensible and open source Platform as a Service (PaaS) that makes application deployments faster and easier. With tsuru, you don’t need to think about servers at all. As an application developer, you can:

• Write apps in the programming language of your choice
• Back apps with add-on resources such as SQL and NoSQL databases, including memcached, Redis, and many others
• Manage apps using the tsuru command-line tool

Links:

• Landing page: https://tsuru.io
• Full Documentation: https://docs.tsuru.io/main/
• How to Contribute: https://docs.tsuru.io/stable/contributing/
• Repository & Issue Tracker: https://github.com/tsuru/tsuru
• Talk to us on Gitter: https://gitter.im/tsuru/tsuru

Popular platforms supported:

• Python
• Nodejs
• GO
• Ruby
• PHP
• Perl
• Lua
• Java

Quick Start

Getting tsuru-client

Download the latest release for your platform at: https://github.com/tsuru/tsuru-client/releases/

Example for release 1.1.1 and OS X:

$ curl -sSL https://github.com/tsuru/tsuru-client/releases/download/1.1.1/tsuru-1.1.1-darwin_amd64.tar.gz | tar xz

Install Guides

• Minikube
• GKE - Google Kubernetes Engine

Testing

If everything's gone well you have the tsuru running in a Kubernetes Cluster. Call app list to see tsuru working, this command needs to return one app called tsuru-dashboard.

$ tsuru app list

diaats's Issues

Clustering support

Add some sort of clustering support, providing some kind of configuration on how images should get deployed and linked.

Add Travis-CI and Drone builds

Along with the ribbons in the README file.

Support dynamic configuration

There should be an administrative API for dynamically add plans and images.

export environment variables defined in the image

Docker supports declaring environment variables in the Dockerfile, these environment variables are then available in containers created using the built image, and are also forwarded when Docker links two containers. Some services use this Docker feature to expose authentication information, and since diaats supports only host and port, it isn't possible to use any service that require authentication at the moment (in other words, diaats works really well with memcached and non-authenticated Redis haha).

We could inspect these environment variables and make then available during bind. That would expand diaats availability to images such as mysql and postgres.