Skip to main content

About Aldryn (legacy)


Aldryn continues to be supported by Divio, but we do not recommend using Aldryn Django for new applications.

The Aldryn Django addons framework is an optional system that allows packages to be installed and configured very easily and in some cases fully automatically.

What are Aldryn addons?

Addons can be thought of as wrappers for Python packages such as Django or django CMS that allow them to take advantage of our addons framework. You'll see for example addons such as Aldryn Django (a wrapper/installer for Django) and Aldryn Django CMS (a wrapper/installer for django CMS).

Aldryn Addons are provided as a convenience. If you'd like Django in your application, with all its settings configured for our infrastructure (uWSGI gateway, database, media storage etc), and in such a way that they will work correctly in the Live, Test and local environments, then Aldryn Django will take care of that for you; if it's installed, all that configuration and wiring will be done automatically.

In the case of Aldryn Django CMS, it will configure settings such as MIDDLEWARE and TEMPLATES automatically.

Packages as installed by Divio addons (such as Django or django CMS) are completely standard and unmodified.

Installation and basic configuration of addons is managed via the application's dashboard in the Control Panel. More advanced configuration can be managed via settings and environment variables.

The Dockerfile in Aldryn Django applications

Hashes (#) in the Dockerfile indicate a comment. Sections within angle brackets are autogenerated by the Divio Control Panel, and may be updated or changed on deployment without warning.

Removing these wrapping tags will prevent a section being populated or changed.

The empty Dockerfile at application creation

The Dockerfile starts life at application creation thus:



# <NPM>
# </NPM>

# </BOWER>



# <GULP>
# </GULP>


These sections are in effect placeholders for Docker commands and configuration that will be used to define the application later.

The <WARNING> section

The <WARNING> is always populated.

# Everything within sections like <TAG> is generated and can
# be automatically replaced on deployment. You can disable
# this functionality by simply removing the wrapping tags.

The <DOCKER_FROM> section

This is determined by the application's base project version. If you update the base project in the application's General Settings in the Control Panel, this will be updated on the next deployment.

For an application built on the aldryn/base-project:py3-3.23 image, corresponding to the Base Project: Python 3 v3.23:

FROM aldryn/base-project:py3-3.23

The <NODE> section

This section will be supplied by a Boilerplate that includes Node components, for example in the django CMS Sass Boilerplate.

An example that uses other files supplied by the Boilerplate (such as to set up the Node environment:

# <NODE>
ADD build /stack/boilerplate


RUN bash /stack/boilerplate/

ENV NODE_PATH=$NVM_DIR/versions/node/v$NODE_VERSION/lib/node_modules \
# </NODE>

The <NPM> section

If package.json (specifying Node packages that should be installed) is present in the root of the application, then instructions will be inserted to copy it to the root of the image and install the packages.

# <NPM>
# package.json is put into / so that mounting /app for local
# development does not require re-running npm install
ENV PATH=/node_modules/.bin:$PATH
COPY package.json /
RUN (cd / && npm install --production && rm -rf /tmp/*)
# </NPM>

The <BOWER> section

If both bower.json and .bowerrc are present in the root of the application, then the deployment process will insert:

COPY bower.json .bowerrc /app/
RUN bower install \
--verbose \
--allow-root \
# </BOWER>

The <PYTHON> section

If is present in the application, then at deployment time the Control Panel will ensure that this section contains appropriate instructions to handle installation of Divio Cloud addons and other packages. The exact contents of this section will depend on the application, for example:

ENV PIP_INDEX_URL=${PIP_INDEX_URL:-${WHEELS_PLATFORM:-aldryn-baseproject-py3}/+simple/} \
COPY requirements.* /app/
COPY addons-dev /app/addons-dev/
RUN pip-reqs compile && \
pip-reqs resolve && \
pip install \
--no-index --no-deps \
--requirement requirements.urls

If requirements.txt is present in the application, then the pip-reqs compile instruction will be removed. See How to pin all of your application's Python dependencies for why you might want to do this.

The <SOURCE> section

The SOURCE section copies the application files to the /app directory of the container.

COPY . /app

We do this late in our Dockerfile by default. This is because it copies the entire repository into the container, meaning that if anything is changed in the repository, it would invalidate all the following layers, which would have to be rebuilt from scratch rather than using cached layers. For reasons of economy, we keep this as late as possible.

If other parts of the repository need to be copied into the container earlier in the process, these should be explicitly specified as required.

The <GULP> section

If gulpfile.js is present in the root of the application, then instructions will be inserted to run the gulp build process:

# <GULP>
ENV GULP_MODE=production
RUN gulp build
# </GULP>

The <STATIC> section

<STATIC> is always populated, with a command to copy static files to the location from where the web server will serve them:

RUN DJANGO_MODE=build python collectstatic --noinput