atomaka/home-applications
1
0
Fork 0
Code Releases Activity
home-applications/Makefile

19 lines
741 B
Makefile
Raw Permalink Normal View History

Setup nginx proxy
2017-12-05 11:10:07 -05:00
deploy: validate files
Initial commit
2017-07-05 21:03:25 -04:00
scp ./*.env 192.168.1.20:/home/atomaka/docker
scp ./docker-compose.yml 192.168.1.20:/home/atomaka/docker
ssh 192.168.1.20 "cd /home/atomaka/docker && docker-compose up -d"
Setup nginx proxy
2017-12-05 11:10:07 -05:00
files:
scp ./nginx.tmpl 192.168.1.20:/home/atomaka
ssh 192.168.1.20 "sudo mv /home/atomaka/nginx.tmpl /mnt/data/docker/nginx/templates/"
Migrate to using host network In order to use upnp and other discovery services, home assistant needs to live on our real network and not inside a Docker network. This is trivial, but triggered an issue with our nginx proxy, which does not support proxying to containers on the host network. This is resolved by adding ANOTHER proxy to transition from the docker "proxy" network to the host network (simply by pointing at the machines IP address). HTTP Request | Dynamic Nginx proxy | Static Nginx proxy | Home assistant application
2018-02-28 20:04:31 -05:00
scp ./nginx.template.conf 192.168.1.20:/home/atomaka
ssh 192.168.1.20 "sudo mv /home/atomaka/nginx.template.conf /mnt/data/docker/haproxy/"
Setup hadashboard
2018-06-01 10:02:40 -04:00
scp ./nginx.template.conf 192.168.1.20:/home/atomaka
ssh 192.168.1.20 "sudo mv /home/atomaka/nginx.template.conf /mnt/data/docker/hadashboardproxy/"
Setup nginx proxy
2017-12-05 11:10:07 -05:00
network:
ssh 192.168.1.20 "docker network create nginx-proxy"
Initial commit
2017-07-05 21:03:25 -04:00
validate:
docker-compose config > /dev/null
Copy permalink