This template runs watchtower. This is new for me so still seeing if i like it! (fingers cross this works, yes need to setuyp smtp email at some point, lol)
none, this container can be cofigured entirely by env vars so i use those
none, no published port is needed
This template runs my infinitude proxy instance. This enables Carrier Inifinity Thermostats to be controlled by API, web page, home assistant etc) One note please for the love of god never buy a carrier heating system with one of these controls they are terrible in my experience. I inherited it, instead buy a nice generic heating/AC system that can support any standard thermostat.
none, this container can be cofigured entirely by env vars so i use those
none, this published port of 4000 for this container oveeride the interall 3000 because i have container that needed 3000 it can be reached by swarmIP:4000
This template runs my cloudflare dynamic DNS updater. It adjust the default container cron job from 5 minutes to 1 minute because i have failover WAN ports.
none, this container can be cofigured entirely by env vars so i use those
none, this need no special port mappings or other considerations consider using an secret to store the API
This is my most complex stack to date. It runs the unifi-poller (uPoller) application consisting of an influx database, grafana dashboard and the uPoller collector.
This has a lot of state (database, provisioning directory for granfa, state for grafana, config file for upoller, etc.)
This time i chose to store each of these in their own glusterfs volume mount using the gluster volumefs driver.
This has the advatages of creating folders that alread have the uid:gid of the grafan container (instead of messing around with chown and chmod)
This is how to install portainer on the swarm you created using this gist note this should work on non-swarm installs too!
Download the portain stack yaml that will do this for you
curl -L https://downloads.portainer.io/ce2-17/portainer-agent-stack.yml -o portainer-agent-stack.yml
This template runs my experimental traefik server for evaluating if i move to it from handcrafted nginx proxy.
traefik requires a static configuration - you need to pick either file based on command line based (or all commands need to be in your stack). you cannot mix these - for example if you put some settigs in a file doing additonal static config via command line then things kike env vars will be ignored i chose to put the static config in a traefik.yml file this seems to be considerd best practice in 2.6 by some i also configured a dynamic files folder - this is for aything that can't or shouldn't be configured in a docker file (middlewares, non-docker related routers etc)
/dev/zwave (add to /etc/udev/rules.d/)See the original instructions here: https://community.home-assistant.io/t/rpi-as-z-wave-zigbee-over-ip-server-for-hass/23006 also see the notes below in each file.
| #!/usr/bin/env python3 | |
| """Command generator for setting DHCP Option 119 | |
| This script converts the specified domain names to DHCP Option 119 | |
| (Domain Search Option) and prints commands for various DHCP servers. | |
| USAGE: | |
| ./dhcp_option119.py DOMAIN ... | |
| EXAMPLE: |
NOTE: as of 9/14/2023 this will only work with a custom patched linux kernel6.5.2 Proxmox have indicated they will back port these patches contact me on the proxmox forum if you wish to roll the patches yourself
Nodel:
10.0.0.81/32fc00::81/128
I use Cloudflare as my external DNS provider and will be using this for my challenge, if you don't use cloudlfare adjust accordingly.
this gist is part of this series
Datcenter > ACMEadd