Deploy based on Procfile

[jairhenrique]

Today, many of my application have more than one entry on Procfile, like this:

web: gunicorn myapp:app --bind 0.0.0.0:$PORT --workers=$GUNICORN_WORKERS --worker-class aiohttp.GunicornUVLoopWebWorker -e SIMPLE_SETTINGS=$SIMPLE_SETTINGS -e DJANGO_SETTINGS_MODULE=$SIMPLE_SETTINGS
worker: celery --workdir=src -A myapp.celery worker --concurrency=$CELERY_WORKER_CONCURRENCY -l info -Ofair --without-mingle --without-gossip --without-heartbeat
admin: gunicorn --pythonpath src myapp.django_wsgi --bind 0.0.0.0:$PORT --workers=$GUNICORN_WORKERS -e SIMPLE_SETTINGS=$SIMPLE_SETTINGS -e DJANGO_SETTINGS_MODULE=$SIMPLE_SETTINGS
beat: celery --workdir=src -A myapp.celery beat -l info -S django

When I deploy my application, I need to run teresa deploy create XXX for each entry of Procfile. What changes in each deploy is the command entry executed in Procfile.

It would be nice if Teresa make one image and deploy for each entry.

Maybe there would be in the settings an association between application and Procfile entry.

[drgarcia1986]

There're some implications, f.ex the build of those applications may be different, practical example the admin app needs to collect statics, but worker don't. Another problem is if you perform a broken build, maybe you broke all of your applications.

I know, it's annoying but is the safe way IMO.

But, we talked about a "build promotion" feature in the future, maybe this feature will help you with this annoying process.

Hey guys (@aguerra @yagonobre ), what do you think about?

[dereke]

We use a similar feature to this but on flynn.
Alongside the Procfile we have an app manifest file which describes the apps envs and routes to create.

https://github.com/featurist/flynn-pr-apps