You’ve crossed me for the last time WordPress. While I appreciate all your years of service, it’s time to go.
While I had found WordPress to be ‘ok’ and there does exist a plugin for everything under the sun.. Every few days I would get a notification that wordpress itself or one of the many diaspora of plugins would need an update, and then invariably something would break. Now I’m spending time not creating content, but just doing admin work trying to find all the places something may have gone wrong. God forbid, the hosting platform needed to upgrade the PHP runtime on the server.
Jekyll has been around for a while, and I’ve been using it a bit over on GitHub. So it was time to take the plunge. Once I got over the initial hump of figuring out how the site was wired together, I was quickly able to get a simple theme together. Now I just needed my content.
I did say that WordPress had a plugin for everything, they even had a plugin for breaking up with WordPress. I installed the Jekyll Exporter plugin, and of course it didn’t work because it was conflicting with some other plugin. Eventually I was able to get it to spit out a zip file with all of my content, I dragged it over into my new project and BAM! Look at that, my whole site is back.
Damn is it fast!
I mean, of course it is, that is the point, you can’t really go faster than static content, but you kinda forget what that means in the modern web. Now that its fast, I also spent five more minutes tweaking a few accessibilty things so I would have 100s across the board in my lighthouse scores. That would have taken me ages in WP.
Sending JSON formatted logstash data into your ELK cluster is great. It is a real help when you are searching through the proverbial haystack in production for clues to what went wrong. However, sometimes when you are developing you might want to read the data off the test server just like it was going to your console … now you hate the JSON format. Tailing the logs is now basically worthless.
Here is a bash script that tails the log and just prints out the ‘@message’ field in the JSON object.
A yeast starter is used to initiate cell activity or increase the cell count before using it to make your beer. The yeast will grow in this smaller volume, usually for 1-2 days, which then can be added to 5 gallons of wort.
Time Required: 30 minutes
Small sauce pot
1000 mL Erlenmeyer flask (pyrex)
Dry Maly Extract (DME)
Stir Plate / Stir Bar
Making A Starter
If using liquid yeast as a source, activate the inner yeast pouch and allow to incubate
Bring 650mL of water to a boil
Remove water from heat
Add 1/2 cup of DME, stir to mix, keep off heat to prevent scorching
Return mixture to heat and gently boil for 15 minutes
Sanitize the flask, scissors, thermometer, funnel, and stir bar
When the mixture has finished boiling, use the funnel to transfer it to the flask
Prepare an ice bath and place the flask into the bath, reduce the temperature of the mixture to 85 degrees (Fahrenheit)
Add the stir bar, yeast, and 1/4 tsp of nutrient to the mixture and cover the mouth of the flask with the aluminum foil
Place on the stir plate and allow to stir for 24 hours
To pitch the starter into a batch of beer remember to swirl the flask to pick up all the sediment, also use a magnet to hold the stir bar at the bottom of the flask to prevent it from falling into the fermentor.