EEA & Eionet documentation hub

Browse documentation for IT-systems used by the European Environment Agency and the Eionet network.

Docker Orchestration for BISE Portal

eea.docker.bise

Installation

  1. Install Docker.

  2. Install Docker Compose.

  3. Install Rancher CLI

Usage

Development

In order to be able to edit source-code on your machine using your favorite editor, without having to do it inside a Docker container, you’ll have to create a new user on your laptop with uid=500 and use this user for development:

    $ sudo useradd -u 500 zope-www
    $ sudo usermod -a -G docker zope-www
    $ sudo su - zope-www
  1. Get the source code:

    $ git clone https://github.com/eea/eea.docker.bise.git $ cd eea.docker.bise/bise-devel
    
  2. Update development stack:

    $ git pull $ docker-compose -f source-code.yml up $ docker-compose pull
    
  3. Start development stack:

    $ docker-compose up -d
    
  4. Start Plone in foreground:

    $ docker-compose exec plone bin/instance fg
    
  5. Within your favorite browser head to http://localhost:8080, add a Plone site and install the following add-ons:

* `EEA Plone buildout profile`   6. Now you are ready to develop Plone Add-ons within `src` folder:

     $ ls -l src/
  1. You can do normal Plone development, including setting breakpoints with ipdb

Deployment

Pre-requirements:

  • Rancher CLI
  • Within Rancher UI register min 1 hosts with label: bise=yes

On your laptop:

    $ git clone https://github.com/eea/eea.docker.bise.git
    $ cd eea.docker.bise

Access rights

To enable Rancher CLI to launch services in a Rancher instance, you’ll need to configure it See related Rancher documentation on how to obtain your Rancher API Keys. Thus:

  1. Via Rancher UI:
* Go to **API Tab** add an **Account API Key**   2. On your laptop configure Rancher CLI:

     $ rancher config
  1. Make sure that you’re deploying within the right environment:

    $ rancher config -p
    

Deploy in production:

    $ rancher up -d

Upgrade:

    $ rancher up -d --upgrade --batch-size 1

…and confirm that the upgrade went well:

    $ rancher up -d --confirm-upgrade

…or roll-back:

    $ rancher up -d --roll-back

Edit this page