The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

  • Twitter Updates

  • My Flickr Stream

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 1,595 other followers

Archive for the ‘DevOps’ Category

Friday Deploys, and other harmful BOFH memes – The Isoblog.

Posted by jpluimers on 2019/06/05

The answer to the meme on the right:

If you are having problems deploying on a Friday, you will have them at any time of the week. Your processes are broken.

Source: [WayBackFriday Deploys, and other harmful BOFH memes – The Isoblog.

via: [WayBack] Friday Deploys and other harmful BOFH memes – they need to die in a fire… – Kristian Köhntopp – Google+

Kristian argues that people finding the meme funny should get fired.

I still find it funny. Both in a way that I’m surprised so many BOFH are still there, as well as being happy that on many occasions I’ve helped making this a thing of the past or at least make organisations aware of the deployment risks and how to cope with them.

Do I need to change? Definitely: life is all about learning new things every day and change because of that.

Do I need go get out of a job or a new job? Likely at some point because life is all about change. Hopefully I’ve learned enough by then to find another gig where – in addition to applying my tech skills – I can spread awareness and knowledge. And learn new things. Did I tell about life is all about learning?

Related: [WayBack] by

Via: [WayBack] @michieltcs: I deploy on Fridays (and maybe you should too):


Posted in Development, DevOps, Power User | 1 Comment »

In operations, code is not your friend. Make things simple, make them boring …

Posted by jpluimers on 2018/11/21

Painful lesson learned a while ago: In operations, code is not your friend. Make things simple, make them boring and make them obvious, and keep an eye on the configuration complexity cloc… – Kristian Köhntopp – Google+

Read the rest of this entry »

Posted in Cloud, Development, DevOps, Infrastructure, Software Development | Leave a Comment »

GitHub – yandex/gixy: Nginx configuration static analyzer

Posted by jpluimers on 2018/10/26

[WayBack] GitHub – yandex/gixy: Nginx configuration static analyzer

Gixy is a tool to analyze Nginx configuration. The main goal of Gixy is to prevent security misconfiguration and automate flaw detection.

Right now Gixy can find:

You can find things that Gixy is learning to detect at Issues labeled with “new plugin”

This helps you prevent an nginx configuration issue that can server too many static content by using ../ in the web request which got a lot of attention last week, but was in fact already found during 2016 HCTF by Aklis, and presented by Orange Tsai (twitter/github/blog) various times in 2018, including [WayBack] 2018.




Read the rest of this entry »

Posted in *nix, DevOps, nginx, Power User, Security | Leave a Comment »

Doing hardware upgrades, infrastructure rearrangements and software updates over this week. Expect some down-time…

Posted by jpluimers on 2018/04/16

This is upgrade/update week, so new disk space, and quite a bit of reorganisation going on.

Expect down-times in various portions of

Secondaries should catch most, but some of the web-sites will be down for a while.


Posted in DevOps, Infrastructure, Power User | Leave a Comment »

EmbarcaderoMonitoring – monitoring the Embarcadero internet related services

Posted by jpluimers on 2018/03/15

Over time, there are lots of complaints about Embarcadero related internet services (like forums, QC, Appanalytics, docwiki, blogsweb site, maintenance) so to track uptime, I’ve created a set of EmbarcaderoMonitoring pages:

This is preliminary work based on my own lists of Embarcadero endpoints combined with some research like [WayBack] dnsdumpster and [WayBack] IdentIPSpy

Underneath, they run on the infrastructure which has a limit of 50 free monitors.

It means I have to:

  • trim this down for relevancy
  • better document the endpoint
  • find correct endpoint targets for the black (disabled) and red (down) entries as a few of them might need tweaking
  • maybe split off an insecure and secure version (now most subdomains have both http and https monitored)

Any ideas on improving this are welcome: please post a comment here on on the resulting G+ thread.

Note it likely won’t show cases like when the website was hacked or TLS certificate issues like in SSLLabs security reports for some embarcadero subdomains. I need to think about a means for those, as it will certainly help monitoring my own infrastructure in a similar way.


Read the rest of this entry »

Posted in *nix, Cloud, Development, DevOps, Infrastructure, Monitoring, Power User, Software Development, Uptimerobot | Leave a Comment »

%d bloggers like this: