Gaudi is a generator of architecture written in Go and using Docker. You can use it to start any type of application, and link them together without knowledge of Docker or system configuration. Using Go, Gaudi can build and start your applications in parallel depending of they dependencies.

Describe any architecture with a simple YAML file (called .gaudi.yml). For instance, for a PHP+MySQL combo:

applications:
    front1:
        type: apache
        links: [app]
        volumes:
            .: /var/www
        custom:
            fastCgi: app

    app:
        type: php-fpm
        links: [db]
        ports:
            9000: 9000
        volumes:
            .: /var/www

    db:
        type: mysql
        ports:
            3306: 3306

Start this environment (with sudo privileges):

gaudi

Gaudi will try to find a .gaudi.yml file in the current folder, and start each application simultaneously, or sequentially if they depend on each other.

go get github.com/marmelab/gaudi

Check that your PATH includes $GOPATH/bin:

export PATH=$GOPATH/bin:/$PATH

The gaudi application starts containers with Docker's commands which requires sudo privileges. Make sure that the GOPATH and GOROOT environment variables are correctly set for the root user (or other user with root privileges).

• --config="" Specify the location of the configuration file
• --stop Stop all applications
• --check Check if all applications are running

Gaudi uses Docker to start all applications in a specific container. It builds Docker files and specific configuration files from different templates. All templates are listed in the templates/ folder, one for each application type.

You can find an example of how to start a Symfony application in the wiki.

The YML file describing the architecture should have a section called applications:.

You can specify what kind of application you want to run:

applications:
    [Application name]:
        type: [one of the listed type below]

Application types are listed below.

When an application depends on another, you can link them together:

applications:
    app1:
        type: varnish
        links: [front1, front2]
    front1:
        type: apache
    front2:
        type: apache

Here the app1 application receives environment variables for each link, as follows:

FRONT1_NAME=/front1/app1
FRONT1_PORT=tcp://172.17.0.215:80
FRONT1_PORT_3306_TCP_PORT=80
FRONT1_PORT_3306_TCP_PROTO=tcp
FRONT1_PORT_3306_TCP_ADDR=172.17.0.215
FRONT1_PORT_3306_TCP=tcp://172.17.0.215:80

To open some ports on an application:

applications:
    front1:
        type: apache
        ports:
            80: 8080

The port 80 in the host machine will be mapped to the 8080 in the container.

You can add you own files by mounting volumes:

applications:
    front1:
        type: apache
        volumes:
            php: /app/php

The php/ folder (absolute or relative to the yml file) will be mounted in the /app/php folder in the application.

If you want to install other apt packets, use the apt_get parameter:

applications:
    app:
        type: apache
        apt_get: [php5-gd, php5-intl]

If you want to run an application not yet supported by Gaudi, you can use a prebuilt image, or an image from the Docker index:

applications:
    server:
        type: nodejs
        links: [redis]
        ports:
            80: 80
        volumes:
            nodejs-redis: /app

    redis:
        type: remote
        image: gary/redis
        path: github.com/manuquentin/docker-redis
        ports:
            6379: 6379

Each application uses a custom section to define its own custom configuration settings.

applications:
    [name]:
        type: varnish
        links: [front1, front2]
    custom:
        backends: [front1, front2]

The backends custom parameter defines which applications are load balanced by Varnish. Theses applications have to be linked together using links.

As a webserver:

applications:
    [name]:
        type: nginx
        links: [app]
    custom:
        fastCgi: app

As a load balancer:

applications:
    [name]:
        type: nginx
        links: [front1, front2]
    custom:
        backends: [front1, front2]

The backends custom parameter defines which applications are load balanced by Nginx. Theses applications have to be linked together using links.

applications:
    [name]:
        type: apache
    custom:
        fastCgi: app

The fastCgi custom parameter points out an application where to forward Fast-CGI scripts.

applications:
    [name]:
        type: mysql
    custom:
        fastCgi: app

This application is a simple php5 service, if you want to use it with Apache or Nginx, use the PHP-FPM one.

applications:
    [name]:
        type: php

applications:
    [name]:
        type: php-fpm

To start a Node.js application, use the after_script parameter. If the after_script is not set, Node.js will run without arguments.

applications:
    [name]:
        type: nodejs
        after_script: node /app/server.js

applications:
    [name]:
        type: jackrabbit

Your feedback about the usage of gaudi in your specific context is valuable, don't hesitate to open GitHub Issues for any problem or question you may have.

All contributions are welcome. New applications or options should be tested with go unit test tool.

Gaudi is licensed under the MIT Licence, courtesy of marmelab.