Explore >> Select a destination
|
You are here 
|
tricht.eu | ||
| | | | |
blog.michal.pawlik.dev
|
|
| | | | | This is a third post in the Smart Home series. See the previous post if you haven't already: https://blog.michal.pawlik.dev/posts/smarthome/zigbee-setup/. Last time I wrote about Zigbee and shown how to control smart home devices. In this post I want to show you one of many ways you can use to expose your HA (Home Assistant) instance to the internet. Why expose? All of the examples in previous posts were referring to local instance of Home Assistant. | |
| | | | |
haruska.com
|
|
| | | | | CloudFlare Tunnels can be used as a reverse proxy with TLS termination in place of something like nginx with acme. This also avoids exposing your home IP address via DNS or needing any NAT / port forwarding on your home router. | |
| | | | |
pulkit.cc
|
|
| | | | | Why Self-Host ? Make use of the Raspberry Pi I had laying around. Experiment with some DevOps stuff. Feels cool to have a server running 24x7 in your home. | |
| | | | |
www.h-i-r.net
|
|
| | | If you travel, or work from the road a lot, you probably have a good reason to set up a travel router and VPN. Travel routers let you create... | ||
