A little history on my website, and the underlying framework I have used -- Middleman. I walkthrough the process on how I deploy the website to GitHub pages using a deployment script.
ActiveJob in Rails provides nice benifits. The background queueing gem Sidekiq allows for tailored options that you cannot use with ActiveJob. This post looks at a project's transition from ActiveJob to Sidekiq, and how to fill the missing functionality of ActiveJob Callbacks. By the end, we come up with a way to contain the callback logic to their own modules without modifying the concrete jobs.
When you are knee deep in Ruby and dealing with objects that you never created it's sometimes a little daunting to trace everything back and figure it all out. Luckly there are a couple techniques in Ruby that can aid you. In particular,
pry is an extreamly powerful tool that you should have in your toolbox.
In a large long-lived git repository there is a lot of history behind the current state of things.
git blame lets you scratch the surface, while
git log lets you dig deeper. The use of
git evolution provides a succient and yet comprhensive approach to understanding the evolution of a range of lines within a git repository.
As a developer its not uncommon to juggle multiple servers that interact with each other during development. Ensuring that each server has the correct port set while working off of
localhost is a cumbersome and error prone issue.
port_map is a ruby utility that provides a simple and almost automatic solution to this problem.