So, I’ve been thinking about this for some time now and discussing it on and off with various people and seeing blog posts about this framework, or that library being the ‘one to use’, and the next big thing etc and I keep thinking “well, this isn’t right… Developers are just Tradesmen… aren’t they?”
So, recently we made the decision to move over to a complete ELK stack set up to handle our Massive Data storage solutions. As part of this change, we introduced a streaming message system called Kafka in to our setup – an easy task, some may think… alas not but I got there!…
Okay, so this is more of a design thought process than anything specific (and not an actual list of functions provided by IKEA or MFI for the older generation) but I thought I’d share something with you I come across quite a lot when reviewing code, pull requests and looking at others work, and that’s what I’ve affectionately called the Flat Pack Function (or lack of).
So I’m working on a few libraries which a number of our applications depend on, and rather than having to commit to Bitbucket, update apps, checkout etc etc I wanted to find a way to set my composer file to use my local dev version of the library instead, and this is it.
So recently I was running through all of the potential CI / CD options in regards to looking for something I could use in our Production Environment and Staging Environment for Continuous Integration / Continuous Deployment and decided to look at TeamCity from JetBrains…
Okay, so I’ve been looking at a way of creating a local self signed SSL so I can test out some scheme work I’ve been doing with secure services and came across a few conflicting bits and pieces on the internet about the best way to do this. Here’s the method that I used and it works well for me…
Okay, so when I was running a LAMP stack in the early days of development, one of my biggest gripes was creating VHOSTS every time I wanted to test a new framework, or develop a new app etc. I know it’s not a massive chore, but it’s enough of a chore for me to think twice about testing something.
When I moved to NGINX things were pretty much the same – which annoyed me even more. I thought “there must be a better and easier way of doing this!” and there is…
After a lot of looking around and what not trying to set up a local Vagrant Aerospike Cluster for testing, I decided to just crack on and do it myself – so I thought I’d share the methodology here in case anyone else is looking for the same set up…
All this was done on OS X (El Capitan) – I’m pretty sure most of it would transfer to another OS as there’s nothing Mac specific involved but as I haven’t tested it, you may need to tweak a few things.
Well, I figured it was probably time I started writing some blogs of the things I find as I go through my tech journey – and maybe I can help some of you out with the things I find…
{switchcaseblog} 