drie documentation

Welcome to the drie documentation. You'll find comprehensive guides and documentation to help you start working with drie as quickly as possible, as well as support if you get stuck. Let's jump right in!

Get Started    Discussions

Create a "drie-ready" app

A few things you need to have in your GitHub repo in order for drie to automatically build it for you

This guide is for users who already have an existing GitHub repo and want to build and deploy their repo to drie. Our recommended way to start with drie is to fork one of our drie starter apps and to add your code to the starter app. This way, you already have a "drie-ready" repo and can see your build running right away. We have drie starter apps for:

If you still want to tweak your existing GitHub repo to work with drie, you need to have these 2 files in your repo:

Depending on the type of app you are running, the file below is highly recommended to include in your repo:


.drie.yml is the main configuration file. This file is where you:

  • add environment variables
  • set cron jobs

Click here for more information regarding .drie.yml


The drie Procfile tells drie what processes to run. For example, here's a typical Procfile to run a NodeJS app

web: node index.js

This tells drie to run a web process, executing the command node index.js.

Here's one for a Rails app:

web: bundle exec puma -t 5:5 -p $PORT -e $RAILS_ENV

For examples of Procfile in other languages and frameworks, please take a look at the drie starter apps.


If your repo has multiple programming languages or frameworks, you can specify them here. For example, if your repo needs a Python and Go environment, you can write this in your buildpack:


It is also recommended to have this file, as you can pin a buildpack to a specific release. For example, drie will build the PHP buildpack on release 95


drie already supports many popular buildpacks by default, so .buildpacks file is optional for many repos. Here are currently supported default buildpacks:

What's Next

If you haven't already done so, you must add your GitHub repo to drie:

Adding an additional repo to drie