Skip to content
This repository has been archived by the owner on May 5, 2020. It is now read-only.

Commit

Permalink
add DOKKU SCALE file and doc
Browse files Browse the repository at this point in the history
  • Loading branch information
Hamza Benhmani committed Sep 17, 2018
1 parent 15ff2ef commit de14096
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 1 deletion.
3 changes: 3 additions & 0 deletions DOKKU_SCALE
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
web=1
worker-default=1
worker-beat=1
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -63,7 +63,7 @@ But please only do this in development, not in a production environment.

In order to have this setup when deploying your dash app to your Dash Deployment Server, your `Procfile` has to execute these three processes (`celery worker`, `celery beat` and the dash app)

In order to run Celery tasks On your Dash Deployment Server, your processes workers have to be running and linked to your dash app. To do this, scale up your app's workers processes (Using the names your have in your `Procfile`):
In order to run Celery tasks On your Dash Deployment Server, your processes workers have to be running and linked to your dash app. To do this, scale up your app's workers processes (Using the names your have in your `Procfile`) - Note that this command is not necessary if you have a `DOKKU_SCALE` file that reflects how many workers are assigned to each process, like in this repository:

```
ssh dokku@YOUR_DASH_SERVER ps:scale APP-NAME worker-default=1 worker-beat=1
Expand Down

0 comments on commit de14096

Please sign in to comment.