Backend services¶

Media storage and delivery¶

See also

• Working with your project’s media storage in Python applications
• How to interact with your project’s media storage

Default file storage on Divio Cloud projects is handled by dedicated storage and hosting providers.These are Amazon Web Services’s S3 service, or a generic S3 hostingservice via another provider. Currently, most projects use Amazon’s own S3 service, with theexception of projects in our Swiss region.

Celery¶

See also

• How to configure Celery on Divio Cloud

Celery asynchronous task queue handling is available as a service, depending onenabled project features.

Once enabled, your project will include four new Docker instances (two on theTest and two on the Live server, unless otherwise arranged with Divio Cloudsupport) each running the Celery workers.

The number of Celery workers per Docker instance can be configured with theCELERYD_CONCURRENCY environment variable. The default is 2. This can beincreased, but in that case, you will need to monitor your own RAM consumptionvia the Control Panel.

Celery on Divio Cloud is handled by the Aldryn Celery addon.Please contact Divio Cloud support for custom queues, more instances or customqueues.

Celery containers¶

The containers running the Celery workers are built using the same image as theweb container.

Celery on the Test server¶

Your project’s Test server will pause after 15 minutes’ inactivity in order tosave resources. This will also pause the Celery workers on the Test site.

Celery on the Local server¶

If you make any local changes to a project’s configuration that need to beaccessible to the Celery workers, you should run docker-compose build torebuild them.

The Celery workers will need to be restarted after code changes, with:

docker-compose restart celeryworker

If celeryworker seems to be taking too long to stop, run:

docker-compose kill celeryworker

原文: http://docs.divio.com/en/latest/background/backend-services.html