Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/reload/drupal-apache-fpm
Apache 2.4 container that uses fpm to handle php-requests
https://github.com/reload/drupal-apache-fpm
docker
Last synced: about 5 hours ago
JSON representation
Apache 2.4 container that uses fpm to handle php-requests
- Host: GitHub
- URL: https://github.com/reload/drupal-apache-fpm
- Owner: reload
- Created: 2016-05-18T19:58:17.000Z (over 8 years ago)
- Default Branch: main
- Last Pushed: 2024-07-22T12:48:09.000Z (4 months ago)
- Last Synced: 2024-07-22T15:13:00.981Z (4 months ago)
- Topics: docker
- Language: Shell
- Homepage: https://ghcr.io/reload/drupal-apache-fpm
- Size: 75.2 KB
- Stars: 0
- Watchers: 5
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Apache FPM container based on phusion
Simple apache-vhost that serves content from /var/www/web - php-requests are
proxied to a linked fpm-container named "fpm" on port 9000.
# Dory
Use the following if you use [dory](https://github.com/FreedomBen/dory) (much of the same applies for [nginx-proxy](https://github.com/jwilder/nginx-proxy) and [dinghy-http-proxy](https://github.com/codekitchen/dinghy-http-proxy) which Dory is based on).
```yaml
environment:
VIRTUAL_HOST: example.docker
VIRTUAL_PORT: 80
# Use the following if you want to handle redirects from http to https yourself.
HTTPS_METHOD: noredirect
```
## Using autogenerated certificates
This require Dory version 1.0.3, use `dory upgrade` to upgrade
If you don't already have a Dory configuration-file, have it generate one by running `dory config` then update the update `ssl_certs_dir` configuration:
```yaml
nginx_proxy:
enabled: true
container_name: dory_dinghy_http_proxy
https_enabled: true
# Update the follow line to point at the dev_certificates
ssl_certs_dir: /.local/share/dev_certificates
image: codekitchen/dinghy-http-proxy:latest
```
Then mount that directory into the apache-fpm container so that its auto-generated certificates will be accessible to Dory.
```yaml
volumes:
- '${HOME}/.local/share/dev_certificates:/cert:rw'
```
Then follow the steps in the mkcert sections to specify which certificates to generate and have your OS trust them.
# mkcert
This image has [mkcert](https://github.com/FiloSottile/mkcert)
builtin.
Install `mkcert` on your host machine and generate and install a root
certificate by running `mkcert -install` on your host machine (one time only).
Mac users should then do (one time only):
```console
$ mkdir -p ~/.local/share && ln -s "$(mkcert -CAROOT)" ~/.local/share
```
Then you add the generated CAROOT as a volume (the path on the host
machine is the output of `mkcert -CAROOT`).
In your `docker-compose.yml` supply one or more host names to be be
used for HTTPS. Host names will be search for in these location and in
this order:
1. environment variable `MKCERT_DOMAINS` (several hostnames separated
by space is possible, you can even supply a wildcard domain),
1. the environment variable `VIRTUAL_HOST` (as used by [Dinghy HTTP
Proxy](https://github.com/codekitchen/dinghy-http-proxy)), or
1. the output of `hostname -f` in the container (which can be set with
the `hostname` and `domainname` options).
Mkcert will always add the IPs of the container to the certificate, so
`curl`'ing HTTPS on the IP should always work.
```yaml
volumes:
- '${HOME}/.local/share/mkcert:/mkcert:ro'
environment:
MKCERT_DOMAINS: "example.docker *.example.docker local.docker"
hostname: example
domainname: docker
```
# Full example configuration
```yaml
volumes:
- '${HOME}/.local/share/mkcert:/mkcert:ro'
- '${HOME}/.local/share/dev_certificates:/cert:rw'
environment:
MKCERT_DOMAINS: "example.docker *.example.docker local.docker"
VIRTUAL_HOST: example.docker
VIRTUAL_PORT: 80
HTTPS_METHOD: noredirect
```