now-compose is a command line interface for developing and deploying applications with docker-compose for zeit now.

Setup

now-compose behaves as a wrapper around docker-compose. To get started, you will need docker and docker-compose setup on your machine. To install these dependencies visit the docker-compose install guide.

Install now-compose:

npm i -g now-compose

Usage

If you're already working on a project using docker-compose you can tell now-compose to use your docker-compose.yml file with the -f flag. Otherwise, rename docker-compose.yml to now-compose.yml. now-compose only supports the docker-compose version 3 config syntax. You can learn more about the syntax at the config reference here if you need to upgrade.

By default, now-compose will look for a now-compose.yml file in the current working directory.

You can then use now-compose as you would use docker-compose. For instance, in a directory with a now-compose.yml file run the following to start all containers defined in your config:

now-compose up -d

or if you want to use a docker-compose.yml file

now-compose -f docker-compose.yml up -d

You can view other commands that now-compose supports by running:

now-compose --help

Example project

To view an example project built with now-compose take a look at the cluster example.

Differences when developing with now-compose compared to docker-compose

There are a couple of small differences to keep in mind when using now-compose vs docker-compose.

The first is networking between containers. Usually for services defined in a docker-compose.yml file you would make requests to another service by requesting a url that has the service's name in the url.

version: "3"
services:
  web:
    build: ./web
    links:
      - api
    ports:
      - 3000:3000
  api:
    build: ./api
    ports:
      - 3001:3001

i.e. in the above example web can make a request to api by requesting http://api. now-compose will handle this for you, however you will want to reference the urls defined in environment variables that now-compose will provide to your application.

| Environment Var | Description | Example | | ----------------- | --------------------------------------------------------------- | -------------- | | NOW_HOST_<NAME> | The url of the service | NOW_HOST_API | | NOW_PORT_<NAME> | The first port defined in your services ports config property | NOW_PORT_API |

The second difference from docker-compose, is that all services defined in now-compose.yml must have a build property defined that points to the location of that service's Dockerfile. Since a Dockerfile must be defined for deployments to zeit now. Any services that do not contain a build property (i.e. reference a docker image) will run locally, but they will be skipped during deployment.

This allows you to setup a database locally for development purposes. But skip the deployment to zeit now.

The third difference is that service names defined in now-compose.yml must not contain special characters. Only letters, digits and '_' are allowed.

Deploying to zeit now

Before you can deploy a project using now-compose to zeit now, you need to provide an API token generated to make requests to the now API on behalf of your account.

Visit the token creation screen and generate a new one for use by now-compose.

You can then deploy your application with:

now-compose deploy --apiKey=<your api token>

You can also provide now-compose an api token by setting the environment variable NOW_API_KEY with the value of your token.

Deployment order

A deployment will be created for each service defined in now-compose.yml in order of the depends_on property set for each service in now-compose.yml.

Any services that are linked (using the "links" property in your application's config) will have the environment variables NOW_HOST_<SERVICENAME> set to the deployment url of linked services. NOW_PORT_<SERVICENAME> will be 443 since zeit only serves requests over https.

Happy Developing 🎉

Contributing

All contributions are welcome.

• Fork this repository to your own GitHub account and then clone it to your local device.
• Uninstall now-compose if it's already installed: npm uninstall -g now-compose
• Link it to the global module directory: npm link

Roadmap

now-compose is still a work in progress and is considered in an "experimental" phase. However, don't let that deter you from actually using it. Once the codebase matures expect support for static and Node.js projects for local development and deployment.

Author

Danny Navarro (@danny_nav)