timothyham

A Short IPv6 Guide for Home IPv4 Admins

This guide is for homelab admins who understand IPv4s well but find setting up IPv6 hard or annoying because things work differently. In some ways, managing an IPv6 network can be simpler than IPv4, one just needs to learn some new concepts and discard some old ones.

Let’s begin.

First of all, there are some concepts that one must unlearn from ipv4:

Concept 1

markrmiller

High level leader sync

Contents

• Overseer yuck

Overseer yuck

• This type of thing should not even be necessary here, but out of scope.

m-radzikowski

#!/usr/bin/env bash

set -Eeuo pipefail
trap cleanup SIGINT SIGTERM ERR EXIT

script_dir=$(cd "$(dirname "${BASH_SOURCE[0]}")" &>/dev/null && pwd -P)

usage() {
  cat <<EOF
Usage: $(basename "${BASH_SOURCE[0]}") [-h] [-v] [-f] -p param_value arg1 [arg2...]

dsmiley

#!/bin/sh
# 
# Utility script to rsync and then open a shell or execute commands on a remote host.
# Tailored a little bit for Lucene/Solr
# @author David Smiley
# https://gist.github.com/dsmiley/daff3c978fe234b48a69a01b54ea9914
set -uex
REMOTEHOST=buildbox
REMOTEPATH="builds$PWD"

janhoy

Solr on Kubernetes on local Mac

This tutorial shows how to setup Solr under Kubernetes on your local mac. The plan is as follows:

1. Setup Docker for Mac with K8S
2. Install an Ingress Controller to reach the cluster on localhost
3. Install Solr Operator
4. Start your Solr cluster
5. Create a collection and index some docuemnts
6. Scale from 3 to 5 nodes

stettix

Things I believe

This is a collection of the things I believe about software development. I have worked for years building backend and data processing systems, so read the below within that context.

Agree? Disagree? Feel free to let me know at @JanStette.

Fundamentals

Keep it simple, stupid. You ain't gonna need it.

asereda-gs

import org.apache.calcite.adapter.jdbc.JdbcSchema;
import org.apache.calcite.jdbc.CalciteConnection;
import org.apache.calcite.runtime.Hook;
import org.apache.calcite.schema.Schema;
import org.apache.calcite.schema.SchemaPlus;
import org.apache.commons.dbcp2.BasicDataSource;

import com.google.common.collect.ArrayListMultimap;
import com.google.common.collect.Multimap;

lizthegrey

default['sshd']['sshd_config']['AuthenticationMethods'] = 'publickey,keyboard-interactive:pam'
default['sshd']['sshd_config']['ChallengeResponseAuthentication'] = 'yes'
default['sshd']['sshd_config']['PasswordAuthentication'] = 'no'

smithje

version: '2'
services:
    zoo-1:
        image: zookeeper:3.4.13
        restart: always
        ports:
          - "2181:2181"
        environment:
            ZOO_MY_ID: 1
            ZOO_PORT: 2181

F21

This is a quick guide of the commands we use to sign someone's GPG key in a virtual key signing party.

Note: The steps cover only the technical aspects of signing someone's key. Before signing someone's key, you must verify their identity. This is usually done by showing government-issued ID and confirming the key's fingerprint

The commands will work for both GPG and GPG2.

I use Julian's key for the examples. His key id is 2AD3FAE3. You should substitute with the appropriate key id when running the commands.

Signing the key

1. List the keys currently in your keyring: gpg --list-keys.