Need to setup gpg-agent first, on OSX I use keychain (it also does ssh-agent)
$ brew info keychain
keychain: stable 2.8.5
User-friendly front-end to ssh-agent(1)
https://www.funtoo.org/Keychain
/usr/local/Cellar/keychain/2.8.5 (7 files, 108.5KB) *
# Clone Repo | |
git clone https://github.com/ThomasKaiser/Check_MK.git | |
cd Check_MK | |
# Remove less common plugins | |
rm -f agents/plugins/monitor-jss-and-macos-updates agents/plugins/city-temperatures agents/plugins/monitor-kerio agents/plugins/smart* | |
# Install dependencies | |
brew install smartmontools osx-cpu-temp |
#!/bin/bash | |
# | |
# This script takes one or more x509 certificates in .PEM format (from | |
# stdin or files listed on command line) and adds helpful "bag | |
# attributes" before each certificate. This makes it easier for | |
# humans to identify the contents of the bundle. | |
# | |
# Requires (g)awk and openssl's x509 command line utility. | |
# | |
# Output fields included can be specified via openssl-x509 options: |
# -*- encoding: utf-8 -*- | |
# requires a recent enough python with idna support in socket | |
# pyopenssl, cryptography and idna | |
from OpenSSL import SSL | |
from cryptography import x509 | |
from cryptography.x509.oid import NameOID | |
import idna | |
from socket import socket |
<?php | |
/** | |
* @file | |
* Basic demonstration of how to do parallel threads in PHP. | |
*/ | |
// This array of "tasks" could be anything. For demonstration purposes | |
// these are just strings, but they could be a callback, class or | |
// include file (hell, even code-as-a-string to pass to eval()). |
/* | |
Automatically click all "Verify your email" links in the welcome e-mail from | |
Nintendo Pokémon Trainer Club's signup e-mails. | |
Only unread emails in inbox will be processed. | |
All processed e-mails will be marked as read if verification was successful, | |
and optionally moved to trash if it's enabled in your settings. | |
How to use: | |
1. Login to Gmail |
route(1)
even exists (and throw ifconfig
out in the same go) because it’s just absolutely frustrating. for probably 98% of what you need, ip(1)
is the cool you care aboutgenerally speaking, these will cover you: ip route
, ip address
, ip link
mtr
> traceroute
> ping
is an order that’s useful for a lot of what you needmtr is nice because you can just let it keep running. press d
in its display to get a running history breakdown of packets. fantastic for intermittent issues!
traceroute is generally known already, but depending on the complexity of your networks in question you may want traceroute-nanog
or similar other ones. some of these are ASN-aware, which is useful.
git config --global alias.lola "log --graph --decorate --pretty=oneline --abbrev-commit --all" |
This document details how I setup LE on my server. Firstly, install the client as described on http://letsencrypt.readthedocs.org/en/latest/using.html and make sure you can execute it. I put it in /root/letsencrypt
.
As it is not possible to change the ports used for the standalone
authenticator and I already have a nginx running on port 80/443, I opted to use the webroot
method for each of my domains (note that LE does not issue wildcard certificates by design, so you probably want to get a cert for www.example.com
and example.com
).
For this, I placed config files into etc/letsencrypt/configs
, named after <domain>.conf
. The files are simple:
var amqp = require('amqplib/callback_api'); | |
// if the connection is closed or fails to be established at all, we will reconnect | |
var amqpConn = null; | |
function start() { | |
amqp.connect(process.env.CLOUDAMQP_URL + "?heartbeat=60", function(err, conn) { | |
if (err) { | |
console.error("[AMQP]", err.message); | |
return setTimeout(start, 1000); | |
} |