Skip to content

Instantly share code, notes, and snippets.

View pineapple-vision's full-sized avatar
🏠
Working from home

pineapple.vision pineapple-vision

🏠
Working from home
View GitHub Profile
@thibaut-d
thibaut-d / docker-compose.yml
Last active October 15, 2022 15:21
wordpress docker-compose.yml with Redis and Traefik
version: '3'
networks:
# enable connection with Traefik
traefik:
external: true
# network for the app
backend:
services:
@thibaut-d
thibaut-d / docker-compose.yml
Last active July 1, 2021 22:59
docker-compose.yml for Traefik
version: "3.3"
networks:
# Allow the use of traefik in other docker-compose.yml files
traefik:
external: true
services:
traefik:
@basoro
basoro / proxmox-proxy
Created May 25, 2019 20:45
Running Proxmox behind a single IP address
I ran into the battle of running all of my VMs and the host node under a single public IP address. Luckily, the host is just pure Debian, and ships with iptables.
What needs to be done is essentially to run all the VMs on a private internal network. Outbound internet access is done via NAT. Inbound access is via port forwarding.
Network configuration
Here’s how it’s done:
Create a virtual interface that serves as the gateway for your VMs:
#!/bin/bash
iatest=$(expr index "$-" i)
#######################################################
# SOURCED ALIAS'S AND SCRIPTS BY zachbrowne.me
#######################################################
# Source global definitions
if [ -f /etc/bashrc ]; then
. /etc/bashrc