We're using it with React and occasionally find the docs lacking (and go looking in the component source for the answers), but otherwise have been happy with it, fwiw :-)
One common suggestion is to not set Bash/shell options in the shebang because if someone runs the script with the interpreter explicitly (e.g. `bash my_script.sh`, rather than `./my_script.sh` (which, ime, is quite common as many people to seem to do it to avoid setting the execute bit, sometimes due to a lack of understanding ime)) then the options won't apply - which isn't fun...
Using `set` (e.g. `set -euo pipefail` as the first line after the shebang) is a common suggestion due to this, and similarly it helps with the `#!/usr/bin/env bash` case where the shebang can't handle additional arguments :-)
There are alternative C libraries that are worth considering, e.g. Zig (which is what Bun itself is written in, afaiu) supports using [musl](https://musl.libc.org) as an alternative to glibc, and musl can be statically linked as well (by contrast to the glibc quasi-static-linking).
We do - and have found it very reliable and I really like it :-)
One of the members of our team finds it more complex when it comes to diagnosing why things aren't running/starting as expected, but that's also down to the complexity we have around s6 with other setup scripts (we use it to manage the full suite of processes in our product).
Hence, they're not the biggest fan of it (and would talk negatively about it), but I _think_ s6 isn't really the culprit and instead the other complexity is.
Although, when things go wrong it can be a little bit harder to chase down than it was with our former manual "start this process" type scripts... But, you can just `./run` the run script which may tell you enough :-)
OpenSSH also supports using a script to get the password if using the `SSH_ASKPASS` environment variable, and being invoked under a non-tty input e.g.
{ echo '#!/bin/sh' ; echo 'echo my_password' ; } > password.sh # don't do it like this :-p
chmod +x password.sh
SSH_ASKPASS=./password.sh DISPLAY= setsid ssh user@host /bin/id
In newer SSH versions `DISPLAY` is not required (but there is a new `SSH_ASKPASS_REQUIRE` environment variable), but in older (e.g. 8.x) versions, then it needs to be set as the default ssh-ask-password was an X11 command, and I believe the logic assumed that scenario.
> they get declined if your account is empty too AFAIK but haven't tested it ;P
Not always, at least some banks will allow you to go into overdraft and then charge a fee (e.g. $15 for Commbank) - so it's worth being cautious about running out.
I remember miscalculating and going into overdraft by a very small amount (e.g. a dollar or two) and then being slugged the overdraft fee - I would've much preferred the transaction to be declined, but that isn't/wasn't the default behaviour.
When we first got it, I used one Easiyo sachet to make one container of yogurt. From then on, I've used 1 heaped tablespoon of the last batch of yogurt and then just milk powder.
My steps:
- Mix ~500ml tap water with 150g of milk powder (just put the lid on and shake vigorously, I always put the water in first as the mixing is much easier).
- Add 1 heaped tablespoon of existing yogurt (the previous batch, or I've used Chobani successfully (I've heard some commercial yogurts work and some don't)).
- Fill (leave 5mm gap at the top) the container with tap water.
- Shake again to mix (less vigorously).
- Add boiling water to maker.
- Put jar in.
- Generally I try to wait 12 hours, sometimes up to 18 when I'm not home.
- Refrigerate and enjoy :-)
I enjoy the yogurt straight, but I wouldn't expect everyone to (it may not be sweet enough) - my wife adds honey or jam and fruit when serving.
(I now actually freeze one tablespoon of yogurt as soon as a batch is done, and use it for the next batch after thawing in the fridge (overnight).)
We have an [Easiyo](https://easiyo.com/collections/frontpage/products/black-yogu...) that cost ~$20AUD, and we use one tablespoon of existing yogurt and ~150grams of milk powder (slightly more than suggested for milk, to make it thicker) to make 1 litre of yogurt at a time. (Just mix those bits; put boiling water in the Easiyo, put the container with the mixture in, wait 12 hours, done - no scolding, no temperature monitoring, super simple :-) )
It's incredibly easy, and now I search for more and more recipes that use yogurt to make different things (eg, flatbreads, cakes, pasta sauces, among lots of other things).
It's super easy and really awesome having yogurt forever available :-)
(iirc) It was originally slid.es and the slides.com domain was added later, I know it's not an answer to your exact question, but slid.es was a pretty good start point too :-)
(It became a defacto go-to tool for slide decks for me because it was so memorable)
LXCFS can be used with Docker as well (although the integration is manual) which can be quite helpful (eg we're using it with docker-compose and find it very helpful)
Yes it does, but it's very transparent - until you run into a few things that make it obvious, eg if you disk-image size limits, or memory limits.
I work with a few people who believed it was native, and used it for quite a while, until things started going wrong and we logged in to the vm to fix them.
The useful thing I've found from this is that "AEG" in Australia is the same as "RIDGID" (orange) in the US and the batteries are compatible.
So I've been able to buy tools that are not available as AEG tools in Australia (ie they're not offered in the product range here). I purchased them skin only to avoid any charger incompatibilities (and use the AEG batteries and charges with the RIDGID tools).
It might work in reverse that buying AEG from Australia is now a cheaper way to get RIDGID tools because the Australian dollar is quite weak compared to the US dollar.
(No need to use bpftrace, just an easy example :-) )