Homec4science
Diffusion invenio-infoscience (iugw2017) Browse

R3600/docs/developers/docker.rst
ec0b8791f866iugw2017

Last Change
Raw File

docker.rst
View Options

.. This file is part of Invenio
Copyright (C) 2015 CERN.
Invenio is free software; you can redistribute it and/or
modify it under the terms of the GNU General Public License as
published by the Free Software Foundation; either version 2 of the
License, or (at your option) any later version.
Invenio is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
General Public License for more details.
You should have received a copy of the GNU General Public License
along with Invenio; if not, write to the Free Software Foundation, Inc.,
59 Temple Place, Suite 330, Boston, MA 02111-1307, USA.
.. _developers-docker:
Docker
======
This page describes how to set up Docker containers for development purposes.
.. image:: /_static/docker-compose-setup.png
Setup
-----
Install Docker_ and `Docker Compose`_. Now run:
.. code-block:: shell
docker-compose -f docker-compose-dev.yml build docker-compose -f
docker-compose-dev.yml up
This builds and runs the docker containers. You can now connect to
`localhost:5000` to see your Invenio installation. The `admin` user does not
have any password.
Should you require a fresh installation and therefore wipe all your instance
data, run:
.. code-block:: shell
docker-compose -f docker-compose-dev.yml rm -f
Debugging
---------
The `docker-compose-dev.yml` enables Werkzeug_, a debugger that automatically
kicks in whenever an error occurs. Stacktraces and debugger terminal are
available via webinterface.
.. image:: /_static/docker-debug.png
Furthermore you can debug MySQL at `localhost:3306`
and Redis at `localhost:6379`. You might want to use flower_ for celery
debugging and analysis as well. Just run the following command to open the
webinterface at port `5555`:
.. code-block:: shell
celery flower --broker=redis://localhost:6379/1
Code changes and live reloading
-------------------------------
As long as you do not add new requirements (python and bower) and only change
files inside the `invenio` package, it is not required to rebuild the docker
images. Code changes are mirrored to the containers. If Flask supports it, on
your system it will automatically reload the application when changes are
detected. This sometimes might lead to timeouts in your browser session. Do not
worry about this, but be aware to only save files when you are ready for
reloading.
As of this writing changing template files do not lead to application reloading
and do not purge caches. As a workaround you can simple alter one of the python
files, e.g. by using `touch`.
Building documentation
----------------------
You can also use the Docker container to build the documentation. This can be
done by attaching to running container:
.. code-block:: shell
docker exec -it invenio_web_1 sphinx-build -nW docs docs/_build/html
.. NOTE::
This needs do be done in a running or initialized container because it
requires that Invenio is set up correctly. Otherwise, the script will break
because of missing access rights.
Running tests
-------------
You can also run tests using the Docker containers. Wait until the containers
finished setup and the webservice is running. Then use:
.. code-block:: shell
docker exec -it invenio_web_1 python setup.py test
Overlays
--------
You might want to use build distribute overlays using Docker. Instead of
creating an entire new image and rewrite everything from scratch, you can the
Invenio Docker image. Start by building the image from a branch or release of
your choice:
.. code-block:: shell
cd src/invenio
docker build -t invenio .
Now go to your overlay and create a Dockerfile that suits your needs, e.g:
.. code-block:: docker
# extend the Invenio base image
FROM invenio:latest
# optional:
# add a maintainer for the docker image
# MAINTAINER Doris Developer <doris@xtra-cool-overlay.org>
# root rights are required
USER root
# optional:
# add new packages
# (update apt caches, because it was cleaned from the base image)
# RUN apt-get update && \
# apt-get -qy install whatever_you_need
# optional:
# add new packages from pip
# RUN pip install what_suits_you
# optional:
# add new packages from npm
# RUN npm update && \
# npm install fun
# optional:
# make even more modifications
# add overlay code and set this as our work directory
ADD . /code-overlay
WORKDIR /code-overlay
# install dependencies but ignore Invenio itself because it is already
# installed in the base image
RUN sed -i '/inveniosoftware\/invenio@/d' requirements.txt && \
pip install -r requirements.txt --exists-action i
# build overlay code
RUN python setup.py compile_catalog
# optional:
# do some cleanup
# step back again
RUN mkdir -p /code-overlay/src && \
chown -R invenio:invenio /code-overlay && \
chown -R root:root /code-overlay/invenio_demosite && \
chown -R root:root /code-overlay/scripts && \
chown -R root:root /code-overlay/setup.* && \
chown -R root:root /code-overlay/src
USER invenio
Notice that this Dockerfile must be located in the directory of your overlay.
You might also want to copy the `.dockerignore` that is provided by Invenio.
Same goes for `docker-compose.yml`, `docker-compose-dev.yml` and the `scripts/`
directory. Do not forget to add additional components if they are required,
e.g. new packages or additional containers like databases. Now you can build
and boot up your overlay:
.. code-block:: shell
cd src/invenio-overlay
docker-compose -f docker-compose-dev.yml build
docker-compose -f docker-compose-dev.yml up
In case you want to populate demo data, e.g. when using the official
invenio-demosite overlay, you run the following command after all daemons are
up and running and the initialization is complete:
.. code-block:: shell
docker exec -it inveniodemosite_web_1 inveniomanage demosite populate \
--packages=invenio_demosite.base --yes-i-know
.. _Docker: https://www.docker.com/
.. _Docker Compose: https://docs.docker.com/compose/
.. _flower: https://flower.readthedocs.org/
.. _Werkzeug: http://werkzeug.pocoo.org/
c4science · Help