remuslazar/docker-neos-alpine repository overview

⁠dimaip/docker-neos-apline⁠ ·

Image info⁠

Opinionated Neos CMS⁠ docker image based on Alpine linux with nginx + php-fpm 7.2 + s6 process manager, packing everything needed for development and production usage of Neos in under 100mb.

The image does a few things:

1. Automatically install and provision a Neos website, based on environment vars documented below
2. Pack a few useful things like XDEBUG integration, git, beard etc.
3. Be ready to be used in production and serve as a rolling deployment target with this Ansible script https://github.com/psmb/ansible-deploy⁠ (I gave up on this deployment method, use 2.x version of this image if you need it, but rather consider full conatiner deployment)

Check out this shell script⁠ to see what exactly this image can do for you.

⁠Usage

This image supports following environment variable for automatically configuring Neos at container startup:

In addition to these settings, if you place database sql dump at Data/Persistent/db.sql, it would automatically be imported on the first container launch. See above for options to automatically download the data from AWS S3. If beard.json file is present, your distribution will get bearded⁠.

The container has the crond daemon running, put your scripts to /etc/periodic or crontab -e.

Example docker-compose.yml configuration:

web:
  image: remuslazar/docker-neos-alpine:latest
  ports:
    - '8080:8080'
    - '1122:22'
  links:
    - db:db
  volumes:
    - data:/data
    # needed only for initial provisioning, if REPOSITORY_URL not set
    # - .:/src/
  environment:
    WWW_PORT: 8080
#    AWS_REGION: eu-central-1
#    AWS_ACCESS_KEY_ID: ...
#    AWS_SECRET_ACCESS_KEY: ...
    REPOSITORY_URL: 'https://github.com/neos/neos-development-distribution'
    SITE_PACKAGE: 'Neos.Demo'
    VERSION: '3.3'
    ADMIN_PASSWORD: 'password'
    IMPORT_GITHUB_PUB_KEYS: 'your-github-user-name'
    AWS_RESOURCES_ARN: 's3://some-bucket/sites/demo/'
    COMPOSER_INSTALL_PARAMS: '--no-dev'
db:
  image: mariadb:latest
  expose:
    - 3306
  volumes:
    - /var/lib/data
  environment:
    MYSQL_DATABASE: 'db'
    MYSQL_USER: 'admin'
    MYSQL_PASSWORD: 'pass'
    MYSQL_RANDOM_ROOT_PASSWORD: 'yes'

volumes:
  data:

⁠Provisioning Process

For initial privisioning the container, you can use the REPOSITORY_URL ENV var. If so, the initialization logic will perform a git clone.

Another alternative is to use a Docker mount or volume. Mount the source dir to /src and make sure not to set the REPOSITORY_URL. Then the init logic will just rsync -a from /src to /data/www-provisioned instead.

⁠Flow/Neos Context

FLOW_CONTEXT will be set to Production by default. For development use a host name with a dev subdomain, like dev.mysite.local, this will use the Development context instead.

⁠Utility scripts

Also this container provides a couple of utility scripts, they are located in the /data folder.

⁠Backups

Each container automatically takes care of daily backing up itself by running the /data/backupDb.sh script, which dumps DB and optionally uploads it to AWS S3. So if you store persistent resources on AWS S3, you are good to go (you should probably additionally backup the contents of S3 to some offline storage, but that's a different story).

⁠Two-step provisioning

You may build pre-provisioned images dedicated for your project from such Dockerfile:

FROM dimaip/docker-neos-alpine:latest
ENV PHP_TIMEZONE=Europe/Moscow
ENV REPOSITORY_URL=https://github.com/sfi-ru/ErmDistr
RUN /provision-neos.sh

It will already pre-install your project by running composer install, so the remaining startup will take about 10s, instead of minutes.