docker-pi-hole/.gitignore

*.sw*
*.pyc
.cache
__pycache__
.tox
.pipenv
.eggs
UNKNOWN.egg-info
.env
ci-workspace
.gh-workspace

# WIP/test stuff
doco.yml
Various changed to docker to make CORS happy and customizable 2016-07-08 06:34:41 +02:00			`.sw`
Fix to debian lighttpd php config #19 w/tests 2016-07-16 23:00:20 +02:00			`*.pyc`
			`.cache`
			`__pycache__`
tox + sped up parallel pytest 2017-10-05 21:24:30 +02:00			`.tox`
Update way too much - Tox py3.7 + pipenv - Python3 Dockerfile.py - Dockerfile.py tags remote instead of just local image names now - Circle.sh instead of in-line circle.yml script breakout - probably other stuff I forgot - Docker images build during the tests should hopefullly now be available at the deploy job workflow thanks to shared docker layers. - Rename aarch64 to arm64 to reduce custom map 2020-01-14 15:37:44 +01:00			`.pipenv`
tox + sped up parallel pytest 2017-10-05 21:24:30 +02:00			`.eggs`
			`UNKNOWN.egg-info`
Update gitignore Signed-off-by: Vincent Perricone <vhp@fastmail.fm> 2019-01-13 04:15:17 +01:00			`.env`
Update way too much - Tox py3.7 + pipenv - Python3 Dockerfile.py - Dockerfile.py tags remote instead of just local image names now - Circle.sh instead of in-line circle.yml script breakout - probably other stuff I forgot - Docker images build during the tests should hopefullly now be available at the deploy job workflow thanks to shared docker layers. - Rename aarch64 to arm64 to reduce custom map 2020-01-14 15:37:44 +01:00			`ci-workspace`
Introduce additional docker tags for the debian version. * Added new docker tag variations to specify the debian version ('stretch', and 'buster'). * Arch images are alway as specific as possible: pihole/pihole:master-amd64-stretch * Multiarch images have both the specific debian version tags as well as the generic non-debian tags: pihole/pihole:master-stretch & pihole/pihole:master * Currently, the non-specific tags point to the 'stretch' images. Eventaully it can be migrated to 'buster'. * Use GitHub actions to do the builds. Although the script names include 'gh-actions' to differentiate them from the 'circle' scripts, there is zero logic that is specific to Github (ie. no Github environment variables). * 'armhf:buster' & 'arm64:buster' has an issue with `ip route get`. I think the issue is related to 'qemu', but I'm not sure. Update the `validate_env` function to only use `ip route get` if `nc` reports something strange. Signed-off-by: Daniel <daniel@developerdan.com> 2020-06-04 23:03:48 +02:00			`.gh-workspace`
alpine nginx pihole working, weighing in at 85.36 MB vs debian 252.4 MB 2016-02-13 20:24:44 +01:00
			`# WIP/test stuff`
			`doco.yml`