shawngmc

[default]
aws_access_key_id=XXXXXXXXXXXXXXXXXXXX
aws_secret_access_key=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
aws_region=us-east-1

dante-robinson

Linux Performance Tweaks

Table of Contents

Reflector Mirrors (Arch Based Only)
Conifgure Pacman (Arch Based Only)
Makepkg Tweaks
Installing Yay (Arch Based Only)
Installing Pamac (Arch Based Only)
Performance Tweaks

jesselawson

#!/usr/bin/env bash

ipset -q flush ipsum

ipset -q create ipsum hash:net

for ip in $(curl --compressed https://raw.githubusercontent.com/stamparm/ipsum/master/ipsum.txt 2>/dev/null | grep -v "#" | grep -v -E "\s[1-2]$" | cut -f 1); do ipset add ipsum $ip; done

# Add any IPs here that may not be in the block list yet:
ipset add ipsum 110.169.9.43

bnhf

Just thought I'd put together some detail on deploying Tailscale using Docker and Portainer. These bits-and-pieces are available elsewhere, but not together, so hopefully this will save someone a bit of time if you'd like to add Tailscale to an existing Docker install:

Here's my annotated recommended docker-compose, to use with Portainer-Stacks. Note that I'm not using a pre-made Auth Key. I started that way, but realized it was very easy to simply check the Portainer log for the tailscaled container once the stack is running. In that log you'll see the standard Auth link that you can use to authorize the container. This way you don't need to create a key in advance, or create a reusable key that introduces a security risk:

version: '3.9'
services:
  tailscale:
    image: tailscale/tailscale
    container_name: tailscaled

henk23

# /etc/caddy/Caddyfile

{
	log {
		output file /var/log/caddy/caddy.log
		format json
	}
}

(logging) {