You're not gonna become a master in your spare time, but you can get decently good at photography in five years of dedicated but non-full-time practice. It's taken me about twice that to get decent, but I fucked around a lot along the way.
You don't need a ton of fancy equipment, but photography does require some gear. I'll limit the gear-buying here to once a year (not counting books).
| # Has your OS/FS/disk lost your data? | |
| # cd to the directory containing your project repositories and run the command | |
| # below. (It's long; make sure you get it all.) It finds all of your git repos | |
| # and runs paranoid fscks in them to check their integrity. | |
| (set -e && find . -type d -and -iname '.git' | while read p; do (cd "$(dirname "$p")" && (set -x && git fsck --full --strict)); done) && echo "OK" | |
| # I have 81 git repos in my ~/proj directory and had no errors. |
| pub fn foo() -> int { 5 } |
| require_relative "test_helper" | |
| require "open-uri" | |
| require "net/http" | |
| class EmojiTest < Blog::Test | |
| def test_no_emoji | |
| posts.each do |post| | |
| content = File.read(post) | |
| refute_match /:[a-zA-Z0-9_]+:/, content, |
Since modern.ie released vagrant boxes, it' no longer necessary to manually import the ova file to virtualbox, as mentioned here.
However, the guys at modern.ie didn't configured the box to work with WinRM. This how-to addresses that, presenting steps to proper repackage these boxes, adding WinRM support. Additionally configures chocolatey package manager and puppet provisioner.
My group_vars/all has this:
ssh_host_keys:
github: |
github.com ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAq2A7hRGmdnm9tUDbO9IDSwBK6TbQa+PXYPCPy6rbTrTtw7PHkccKrpp0yVhp5HdEIcKr6pLlVDBfOLX9QUsyCOV0wzfjIJNlGEYsdlLJizHhbn2mUjvSAHQqZETYP81eFzLQNnPHt4EVVUh7VfDESU84KezmD5QlWpXLmvU31/yMf+Se8xhHTvKSCZIFImWwoG6mbUoWf9nzpIoaSjB+weqqUUmpaaasXVal72J+UX2B+2RPW3RcT0eOzQgqlJL3RKrTJvdsjE3JEAvGq3lGHSZXy28G3skua2SmVi/w4yCE6gbODqnTWlg7+wC604ydGXA8VJiS5ap43JXiUFFAaQ==
myserver1: |
myserver1.example.com ssh-rsa AAA...
myserver1.example.com ssh-dss AAA...
myserver1.example.com ssh-ecdsa-sha2-nistp256 AAA...
myserver2: |
| def a l = def b; <<-NIGHTMARES; end; puts send l; end | |
| 😱😱😱 | |
| NIGHTMARES | |
| a |
| // ==UserScript== | |
| // @name Jitai | |
| // @version 1.3.2 | |
| // @description Display WaniKani reviews in randomized fonts, for more varied reading training. | |
| // @author Samuel (@obskyr) | |
| // @copyright 2016-2018, obskyr | |
| // @license MIT | |
| // @namespace http://obskyr.io/ | |
| // @homepageURL https://gist.github.com/obskyr/9f3c77cf6bf663792c6e | |
| // @icon http://i.imgur.com/qyuR9bD.png |
These instructions are for implementing HTTPS on a NFSN-hosted static site using a certificate from Let's Encrypt. The certificate is generated manually on a separate computer.
Start off by installing the letsencrypt client. This requires sudo privileges and will install a bunch of packages:
% curl -O https://dl.eff.org/certbot-auto
% chmod +x ./certbot-auto
% ./certbot-auto
Generate the certificate. This will require you to publish some challenge responses on NFSN. I find it easiest to use tmux with letsencrypt running in one window and an SSH session to NFSN in another:
| # In order for gpg to find gpg-agent, gpg-agent must be running, and there must be an env | |
| # variable pointing GPG to the gpg-agent socket. This little script, which must be sourced | |
| # in your shell's init script (ie, .bash_profile, .zshrc, whatever), will either start | |
| # gpg-agent or set up the GPG_AGENT_INFO variable if it's already running. | |
| # Add the following to your shell init to set up gpg-agent automatically for every shell | |
| if [ -f ~/.gnupg/.gpg-agent-info ] && [ -n "$(pgrep gpg-agent)" ]; then | |
| source ~/.gnupg/.gpg-agent-info | |
| export GPG_AGENT_INFO | |
| else |