Procfile

This is a Go library for parsing the Procfile format.

Formats

Standard

The standard Procfile format is what you're probably most familiar with, which maps a process name to the command to run. An example of a standard Procfile might look like:

web: ./bin/web
worker: ./bin/worker

The standard Procfile format is specified in https://devcenter.heroku.com/articles/procfile.

Extended

The extended Procfile format is Empire specific and implements a subset of the attributes defined in the docker-compose.yml format. The extended Procfile format gives you more control, and allows you to configure additional settings. An example of an extended Procfile might look like:

web:
  command: ./bin/web
scheduled-job:
  command: ./bin/scheduled-job
  cron: '0/2 * * * ? *'

Attributes

Command

Specifies the command that should be run when executing this process.

command: ./bin/web

Cron

When provided, signifies that the process is a scheduled process. The value should be a valid cron expression. See http://docs.aws.amazon.com/AmazonCloudWatch/latest/events/ScheduledEvents.html for details on the cron syntax used in Procfiles.

cron: * * * * ? * // Run once every minute

Noservice

When provided, signifies that the process is an "operational" one off command. These processes will not get any AWS resources attached to them.

This can be used to alias a common command, or by enforcing whitelisting of commands for emp run.

noservice: true

Ports

This allows you to define what ports to expose, and what protocol to expose them with. This works similarly to the ports: attribute in docker-compose.yml.

ports:
  # Map port 80 on the container, as port 80 on the load balancer, using the default protocol.
  - "80"
  # Map port 8080 on the container, as port 80 on the load balancer, using the default protocol.
  - "80:8080"
  # Map port 5678 on the container, as port 5678 on the load balancer, using the tcp protocol.
  - "5678":
      protocol: "tcp"

Environment

This allows you to set process specific environment variables. If these are set with emp set, the value within the Procfile will take precendence.

environment:
  EMPIRE_X_LOAD_BALANCER_TYPE: "alb"

See documentation about deploying an application for a list of other supported environment variables.

ECS

This allows you to specify any ECS specific properties, like placement strategies and constraints:

ecs:
  placement_constraints:
    - type: memberOf
      expression: "attribute:ecs.instance-type =~ t2.*"
  placement_strategy:
    - type: spread
      field: "attribute:ecs.availability-zone"

See http://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-placement.html for details.