DTEKT.IO, a website uptime and performance monitoring tool, just released a sandbox environments that allow anyone to test the service without registering and typing any usernames or passwords. Just go to https://dtekt.io, fill in your website address and click on "Start your sandbox" button and you will be redirected to a personalized DTEKT.IO account that has preconfigured monitors and alerts ready to be explored!

Hello, I've just released together with my fella a new tool for website uptime and performance monitoring. It is divided into two categories:

- Performance Monitors - Allows for tracking over period of time performance metrics like WebVitals, number and size of website external calls, SpeedIndex or other front performance related metrics, - Uptime Monitors - Allows for uptime monitoring of public endpoints. HTTP, PING, and TCP checks are available. The HTTP check provides a lot of useful details like cert expiration, waterfall view of the entire HTTP session. Allows for creating alerts that - currently - can alert you on the slack channel.

Free plan included, for paid plan for testing as entire development team contact me at [email protected]. If you have a feedback please use the Feedback form which you can find in the menu. Any feedback appreciated!

Cheers :)!

'cmd && do_sth || do_sth_else' is not equivalent to if else

https://mywiki.wooledge.org/BashPitfalls#cmd1_.26.26_cmd2_.7...

Do yourself a favor and read the linked section. The "elegant" method sure can be nice, but comes with a downside you really need to be aware of.

I love shell scripting and this highlights one of the major problems with bash: small changes like this can appear completely interchangeable with other mechanisms for doing the same thing but introduce edge cases that can unexpectedly bite you.

For example... consider what happens if "[ $foo -eq 0 ] && /bin/do-something" is the last statement within a function or the end of your script.

I came here to make this comment. It really needs to be a top-level comment and at the top.

I have wasted many hours of my life tracking down buts where the idiom in the OP was used in a function. It leads to really hard to find bugs.

Beware!!!

I cannot believe this is not at the top. Short-circuiting is useful and fun in places, but to suggest it as a general replacement for conditionals as the OP does is absolutely wrong and will cause bugs.

Does this caveat still apply when you only use a single short-circuit operator in a given command? As a long time shell scripter I'd honestly be a little afraid to use more than one at a time.