{{ !articles[0].partner.isSponsoringArticle ? "Platinum" : "Portal" }} Partner
architects,devops,tips and tricks

Can you spot the configuration difference?

One of our Dev (DevOps?) guys came across this inconsistency that broke a server, and said in scrum “without Metafor this totally would have taken me 5 hours to identify”. We got discussing various little slip of the pinky errors that can completely break a server. You know, extra/missing/wrong character in the config: nameserver, port, whatever. Or maybe your pinky slipped and suddenly your sources list has you grabbing from the wrong repo.

These types of config bugs can be a massive pain to identify. Looking through the config code line by line is bad enough, but a double key tap when you meant a single can create a mess our eyes generally suck at picking out – the ol’ golden needle in a haystack situation.

Oh, they call you “eagle eyes” around the office do they? I thought you might enjoy a little game of spot the difference :)

configuration difference

Hmmmmmmm, the times are different, that’s suspicious…

content difference

Now just imagine what a pain it would have been to pick out that bug if we didn’t find it and highlight it in yellow for you. To receive your diff report like the one above, join the Metafor Beta.

Published at DZone with permission of {{ articles[0].authors[0].realName }}, DZone MVB. (source)

Opinions expressed by DZone contributors are their own.

{{ tag }}, {{tag}},

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}
{{ parent.authors[0].realName || parent.author}}

{{ parent.authors[0].tagline || parent.tagline }}

{{ parent.views }} ViewsClicks