OpsCrash Episode #3 – Better late than never
May 26, 2016
We’re continuing our hat-trick streak of weekly OpsCrash episodes. Episode #3 was recorded on Sunday May 22nd, but the posting got a little delay due to… slackers. We managed to finally limit ourselves to just 23 minutes of witty banter covering the latest in: nano wins at SSH, GitLab love fest, custom ASIC for fun and profit, governments always make the best IT choices, dipping your servers in Ranch, and a special bonus.
Pushing successful SSH logins to PushBullet
January 25, 2016
On Friday I ran across Sandrino Di Mattia’s post “Posting successful SSH logins to Slack” which was very easy and a very nifty idea. Already most of my notifications from various systems (Datadog, Tutum, Twitter, etc) are gathered into a notification channel on Slack, so I jumped on the chance to try out this script. It worked great, but I realized there was one major issue: my slack notifications are plentiful and passive. I have only a few internet accessible servers and I care about them a great deal, so I want to know if anyone is accessing them (since it should only be me). So I added push notifications for successful SSH logins!
Simple and automatic Github deployment using PHP
September 11, 2015
If you’re like me, every project you work on worth anything gets put in GitHub. It’s safe and you get all the benefits of using Git. Of course those benefits include deployment hooks, if you’ve got the system setup for it. On small projects it may seem like it’s more hassle to setup deployment hooks, after all SFTP is simple enough, however it’s actually quite easy to do and only take a few minutes to setup. My use case is JonDavis.name (which is kept in a private GitHub repo) and this has made life much easier for me, even for a single-page website.
Automated Screen Launch
September 13, 2011
At my previous company I set myself up a screen server as mentioned in my previous post, “A screen/shell server is awesome!”. There were only a half dozen servers there so if the screen server got rebooted, it wasn’t a big deal to get my sessions back up and running. At my new company we use virtual machines, so there are quite a number more “servers” to connect to. As I was setting up my screen server, I realized that I didn’t want to deal with the hassle of reconnecting them all, so I sought an automated solution.
WordPress: Enabling SSH/SFTP Updates
June 29, 2010
The first time I dealt with WordPress was when I first started doing IT administration for FanHistory. At that point in time I knew nothing about it and it was breaking horribly. Luckily I managed to fix the issues (which turned out to be Varnish proxy related) and get it standing mostly on its own two feet. One of “minor annoyances” I ran into then and absolutely had to figure out during my migration, was the lack of SSH or SFTP based updates. By default when you go into add or update the plugins (or the software itself) you have only two options FTP and FTPS (SSL). I run neither of these, FTP is majorly old and very insecure. FTPS is just not common. I thought I was stuck doing things manually, until I found out…. You can enable SSH2 based updates in WordPress. Better yet, it is SUPER easy.
Backing up/Migrating PuTTY
June 10, 2010
If you regularly use SSH/Telnet from Windows, you probably use PuTTY. If you don’t use PuTTY, you either should, or your paying too much. Anyways, if you use it a fair amount you probably have saved sessions. While PuTTY doesn’t have an internal mechanism for backing up these settings, it turns out it is very easy. All the settings are stored in the registry. There are two easy methods if you want to back them up (which is always good to do). Afterward you can reload them onto another machine, should you need/desire to do so: