Not intended as a guide for newbies, more like a "cheat sheet" for the somewhat experienced IRC user, especially one who wields some power over a channel.
/join #channel
- Joins the specified channel.
/part #channel
- Leaves the specified channel.
dd if=openSUSE-12.1-DVD-x86_64.iso | pv --eta --size 4628414464 --progress --bytes --rate --wait > /dev/sdc |
On Twitter the other day, I was lamenting the state of OCSP stapling support on Linux servers, and got asked by several people to write-up what I think the requirements are for OCSP stapling support.
Support for keeping a long-lived (disk) cache of OCSP responses.
This should be fairly simple. Any restarting of the service shouldn't blow away previous responses that were obtained. This doesn't need to be disk, just stable - and disk is an easy stable storage for most server
As per the unspoken JB IRC Rule, the mods will also make it up as they go along if they want, Really it doesnt matter, its just to prevent arguments
# I had a bit of trouble getting my unifi controller (hosted offsite) to use a proxy/letsencrypt. So here are the fruits of my labor. | |
# The unifi default port is 8443 running on localhost. | |
# License: CC0 (Public Domain) | |
server { | |
# SSL configuration | |
# | |
listen 443 ssl default_server; | |
listen [::]:443 ssl default_server; |
DUMP | |
// pod-name name of the postgres pod | |
// postgres-user database user that is able to access the database | |
// database-name name of the database | |
kubectl exec [pod-name] -- bash -c "pg_dump -U [postgres-user] [database-name]" > database.sql | |
RESTORE | |
// pod-name name of the postgres pod | |
// postgres-user database user that is able to access the database | |
// database-name name of the database |
According to this cloudflare blog article "Load Balancing without Load Balancers", we can build a rock-solid load balancer only using a router. All the magic comes from BGP and Equal-Cost Multi-Path routing.
In this howto, I will use bird
as BGP router on linux instance (ie. servers).
I use GNS3 with this architecture :
virt-install \ | |
--name=centos-compute-$i \ | |
--ram=32768 \ | |
--vcpus=16 \ | |
--cpu host-model-only \ | |
--os-type linux \ | |
--os-variant centos7.0 \ | |
--import \ | |
--disk path=/var/lib/libvirt/images/centos74-compute-$i.qcow2,bus=virtio,cache=none,format=qcow2,bus=virtio \ | |
--network type=direct,source=enp6s0f0,source_mode=bridge,model=virtio \ |
### Flatpak Repos | |
List packages on a repo : | |
flatpak remote-ls repon-name --user | |
flatpak remote-ls | |
Install packages : | |
flatpak --user install repo-name package-name io.liri.Platform | |
Flathub: |