https://github.com/dlueth/qoopido.docker.apache2
https://github.com/dlueth/qoopido.docker.apache2
Last synced: over 1 year ago
JSON representation
- Host: GitHub
- URL: https://github.com/dlueth/qoopido.docker.apache2
- Owner: dlueth
- Created: 2015-06-01T16:58:31.000Z (about 11 years ago)
- Default Branch: master
- Last Pushed: 2016-12-22T11:47:11.000Z (over 9 years ago)
- Last Synced: 2025-01-25T08:08:22.805Z (over 1 year ago)
- Language: ApacheConf
- Size: 54.7 KB
- Stars: 0
- Watchers: 3
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# recommended directory structure #
Like with my other containers I encourage you to follow a unified directory structure approach to keep things simple & maintainable, e.g.:
```
project root
- docker-compose.yaml
- htdocs
- config
- apache2
- initialize.sh (if needed)
- sites-enabled
- ...
- data
- apache2
- certificates
- logs
```
# Example docker-compose.yaml #
```
web:
image: qoopido/apache2:latest
hostname: [hostname]
ports:
- "80:80"
- "8080:8080"
- "443:443"
volumes:
- ./htdocs:/app/htdocs:z
- ./config/apache2:/app/config:z
- ./data/apache2:/app/data:z
```
# Or start container manually #
```
docker run -d -P -t -i -p 80:80 -p 443:443 \
-h [hostname]
-v [local path to htdocs]:/app/htdocs:z \
-v [local path to config]:/app/config:z \
-v [local path to data]:/app/data:z \
--name web qoopido/apache2:latest
```
# Configuration #
The container comes with a default configuration for Apache2 under ```/etc/apache2/apache2.conf```. The container comes with a default site-configuration for ```/app/htdocs``` for SSL and non-SSL.
Any files mounted under ```/app/config``` will be symlinked into the container's filesystem beginning at ```/etc/apache2```. This may be used to overwrite the container's default configuration with a custom, project specific configuration to (e.g.) include php fpm fastCGI proxy (which requires linking a php fpm container). The current hostname is provided as an environment variable for Apache2 so that ```${HOSTNAME}``` may be used in any Apache configuration.
If you need a custom shell script to be run on start or stop (e.g. to set symlinks) you can do so by creating the file ```/app/config/up.sh``` or ```/app/config/down.sh```.
SSL certificates will be auto-generated per hostname if no key/crt file can be found in ```/app/data/certificates/[hostname].[key|crt]```.