Failed to get D-Bus connection

After setting up the systemd service for Caddy, I received the following error when trying to start the service: $ sudo systemctl start caddy.service Job for caddy.service failed. See 'systemctl status caddy.service' and 'journalctl -xn' for details. $ systemctl status caddy.service Failed to get D-Bus connection: No such file or directory The fix was pretty easy. It turns out that dbus was not installed on the system. I installed it and then the service worked perfectly:...

May 28, 2017

Weekend Reading for Dec 04

Here’s a curated list of the articles I read this weekend. Negative feedback antipatterns Charles-Axel shares a template for providing negative feedback in a constructive manner. via Software Lead Weekly The Books I Recommend For The New Manager I purchased Managing Oneself after reading this post. Google Play had it for less than $7. via Software Lead Weekly Visual Studio Development – Productivity Enhancements in Visual Studio 2017 RC Check out some of the productivity enhancements coming in the new Visual Studio....

December 5, 2016

Introducing Rager

Rager is service that notifies you when the projects you care about most publish a new release. After signing up using your GitHub account, you can start “watching” your favorite projects hosted by GitHub, NuGet or npm. Every night Rager scans for new releases. If it finds one that you are “watching”, it sends you an email with a link to the new release! This application is a side project that I’ve been tinkering with for a while now....

April 10, 2016

Reevaluate Your Log Levels

Constantly reevaluate the logging level applied to log events. Your typing was not directed by angels and your code was not ordained by God when you selected warning as the level for your log event. That code is up for change just like the rest. Too often I see piles of log events with poorly assigned log levels. If there’s an error event flooding your logs that you have no intention to fix, change the logging level....

September 12, 2015

Vagrant Hostsupdater Requires Admin

VagrantPress and VVV use the Vagrant::Hostsupdater plugin to allow you to access your development WordPress sites at a friendlier URL (e.g. http://vagrantpress.dev instead of http://localhost:8080). On Windows machines, the plugin updates the file at C:\Windows\System32\drivers\etc\hosts, but modifying this files requires admin access. You must run your shell as an administrator for the plugin to be able to update this file when you vagrant up. BONUS: I’ve seen a lot of people installing Cygwin or Putty just to be able to use Vagrant on Windows (since it requires SSH)....

July 12, 2015