title: Heroku dynos: can I technically use less dynos in my Django setup?
body: <p>I'm using the following with my Django application:</p>
  
  <ol>
  <li><a href="https://channels.readthedocs.io/en/latest/" rel="nofollow noreferrer">Django channels</a></li>
  <li><a href="http://www.celeryproject.org/" rel="nofollow noreferrer">Celery with both regular and periodic tasks</a></li>
  <li>Deployed on Heroku</li>
  </ol>
  
  <p>My Procfile looks like this:</p>
  
  <pre><code>web: daphne artist_notify.asgi:channel_layer --port $PORT --bind 0.0.0.0 -v2
  worker: python manage.py migrate --noinput &amp;&amp; python manage.py runworker -v2
  celerybeat: celery -A artist_notify beat -l info
  celeryworker: celery -A artist_notify worker -l info
  </code></pre>
  
  <p>This combination seems to be expensive, and I'm wondering if I can make it better. I tried combining <code>celerybeat</code> and <code>celeryworker</code> (with <code>&amp;&amp;</code>) into one dyno called <code>celery</code>, like so:</p>
  
  <pre><code>celery: celery -A artist_notify beat -l info &amp;&amp; celery -A artist_notify worker -l info
  </code></pre>
  
  <p>But that doesn't work, although other <code>&amp;&amp;</code> combinations do work. I'm wondering if I can maybe combine the workers from <code>worker</code> and <code>celeryworker</code>?</p>