History

paul121 1af8413441 Require 2.x-dev if 2.x is requested.		2021-03-24 07:26:57 -04:00
..
dev	Exclude Sniffs that prevent blank lines after comments.	2021-03-11 16:37:18 -05:00
Dockerfile	Issue #3186530 : Inherit from the drupal:9-php7.4-apache image.	2021-03-11 16:37:18 -05:00
README.md	Installing farmOS documentation.	2021-02-25 23:50:46 -05:00
build-farmOS.sh	Require 2.x-dev if 2.x is requested.	2021-03-24 07:26:57 -04:00
docker-compose.development.yml	Update Dockerfile, docker-compose.development.yml, and docs for XDebug 3.	2020-12-04 14:24:12 -05:00
docker-compose.production.yml	Add `restart: always` to docker-compose.production.yml.	2021-02-25 22:30:54 -05:00
docker-compose.testing.mariadb.yml	Use a test matrix to run tests and site-install against MariaDB/SQLite/Postgres in parallel	2021-01-18 14:31:39 -05:00
docker-compose.testing.pgsql.yml	Use a test matrix to run tests and site-install against MariaDB/SQLite/Postgres in parallel	2021-01-18 14:31:39 -05:00
docker-compose.testing.sqlite.yml	Use a test matrix to run tests and site-install against MariaDB/SQLite/Postgres in parallel	2021-01-18 14:31:39 -05:00
docker-entrypoint.sh	Wait only as long as necessary for Postgres and the farmOS file copying to be done	2020-11-27 06:53:07 -05:00

README.md

Running farmOS with Docker

This directory contains files necessary to build the farmOS Docker image, along with example docker-compose.yml files that can be used for running farmOS in Docker containers.

Development environment

To run a farmOS development environment, copy docker-compose.development.yml into a new directory on your server, rename it to docker-compose.yml and run docker-compose up.

This example mounts a local www directory on the host as a volume in the container at /opt/drupal, which allows for local development with an IDE.

Production environment

To run a farmOS production environment, use docker-compose.production.yml as an example for building your own configuration. Note that this example does not include a database. It is assumed that in production environments the database will be managed outside of Docker.

This example mounts a local sites directory on the host as a volume in the container at /opt/drupal/web/sites, which contains the site-specific settings and uploaded files. This allows a production farmOS instance to be updated by simply pulling a new image (and then manually running database updates via Drush or /update.php). Everything outside of the sites directory will not be preserved and will be replaced with the new official farmOS files.

For more information, see https://docs.farmOS.org/hosting.