Via Jason Snell, the f.lux folks have documented the process of getting f.lux onto your iPhone without jailbreaking. The process is legitimate; it uses Xcode and the new provisions in the Apple developer program. It’s a bit complicated, so you may just chose to do what I do, and wear cheap sunglasses with yellow lenses.
(For why you would care about any of this, check out Blue light has a dark side at Harvard Health.)
Listening to: The It Follows soundtrack by Disasterpeace
Reading: Star Wars: Aftermath. Having a hard time getting into it, though. Stuck about half way through.
Playing: Downwell.
(Image nicked from the linked Downwell review.)
If you have a Mac, you should definitely get this app. It changes your wallpaper to a random selection from Unsplash after a configurable interval.
irvue
Source: Irvue for OS X
I’ve moved on from ps aux | grep -i processname; kill PID. The Mac (along with many other Unix-likes) has two handy utilities: pgrep and pkill. pgrep does a case-insensitive search for processes matching the expression you provide, and returns all matching PIDs, one per line. pkill does the same search, but just kills the matching processes instead of returning the PIDs.
A common use case for me is middleman hanging when I change the config.rb. I could kill it using the following:
kill `pgrep middleman`
pkill middleman
One of the benefits of using pkill is that you can run the command interactively. Handy if you end up searching on the scripting language running the process, rather than something a bit more unique.
Below is the process required for setting up password-free sign in for “user” at a server called “foo.com”. I’ve added links to “Explain Shell” throughout so you can see an overview of what the commands and arguments do.
First, create your .ssh directory by issuing the command mkdir -m 700 -p ~/.ssh.
Secondly create the keypair: ssh-keygen -t rsa -b 2048 -f ~/.ssh/foo.com The filename (foo.com) can be anything you want, but it’s easiest to use a name that hints at for what server you’ve generated the keys.
You’ll be prompted for a passphrase for the key. This isn’t required, but is recommended. You can generate and store your passphrase in your OS’s keychain manager. The Mac has Keychain. Linux offers KWallet or Seahorse. You can also use a password manager like 1Password. Keep in mind, though, that using a password manager will likely negate the “passwordless” bit of the process unless it has the kind of OS integration the aforementioned keychain managers have.
You’ll now have two key files in ~/.ssh: a private key called foo.com and a public key called foo.com.pub.
Next, you need to add the public key to the remote server to which you’d like to sign in. To do that, use the script ssh-copy-id. If you’re on a Mac, you need to first get that script via homebrew. Install brew, then run brew install ssh-copy-id.
Push the key up to foo.com by issuing the command ssh-copy-id -i ~/.ssh/foo.com.pub user@foo.com. When prompted for a password, use the password you normally use to sign on to the system, not your key’s passphrase.
The sign into the remote system using the new keypair, use the command ssh -i ~/.ssh/foo.com.pub user@foo.com. The first time you do so, your OS will prompt you for the passphrase. Enter it, and allow your OS to save the passphrase to the keychain for passwordless log in.
Once the credentials have been added to the remote system, it’s handy to add the host, user, and key to your ssh config. Detailed instructions can be found on Nerderati.