Our great sponsors
-
httpie
🥧 HTTPie CLI — modern, user-friendly command-line HTTP client for the API era. JSON support, colors, sessions, downloads, plugins & more. (by httpie)
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
libelektra
Elektra serves as a universal and secure framework to access configuration settings in a global, hierarchical key database.
-
-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
Yesterday I was wondering why the self signed root certificate and the certificates I added to my debian installed didn't work with httpie (ssl warning) but did work with curl (and the browsers I added the RootCA to).
I found the explanation: https://github.com/httpie/httpie/issues/480 httpie doesn't look into /usr/local/share/ca-certificates but apparently it's not httpie's fault, it's the python requests library that doesn't check that folder.
I don't know what to think of it and who is supposed to fix it. But I am back to curl with my tail between the legs (because I oversold httpie to my coworkers) for now. There's only one place where the bucket stops with curl.
macOS has something similar also with defaults [1].
https://macos-defaults.com/#%F0%9F%99%8B-what-s-a-defaults-c...
It should also report the syntax and so on, and actually you want a way to directly modify configuration values. So if you think this through, you will end up with something like https://www.libelektra.org
Have you seen https://dagger.io/? Managing all that with code has been a life changer to me.
CONNECT_SSL_ENDPOINT_IDENTIFICATION_ALGORITHM and CONNECT_SASL_MECHANISM.
And very importantly, don't forget CONNECT_SECURITY_PROTOCOL, as not only will you have odd connection failures (usually manifests as the client dying at the ApiVersions negotiation stage of the Kafka protocol's handshake), but because a script run in the image uses the value of that undocumented setting to execute a prerequisite in different ways [2], and you'll get weird behaviour that obscures the real issue.
2) Support more than one way of configuring things - maybe I want to mount in a config file, maybe I want to provide a ConfigMap, maybe I want to do it via env vars. Well... [3]
[0]: https://strimzi.io/docs/operators/latest/deploying.html#ref-...
[1]: https://docs.confluent.io/platform/current/installation/dock...
[2]: https://github.com/confluentinc/kafka-images/blob/master/kaf...
[3]: https://strimzi.io/docs/operators/latest/deploying.html#asse...
https://github.com/spieglt/whatfiles may be useful to find such files
The UNIX filesystem has traditionally been a graph for ever. I haven't looked at details for a couple of decades, but definitely all UNIX/POSIX/Linux filesystems operate on a graph model.
A distinction I used to make when I was teaching this stuff: on your filesystem tree, on Unix names (labels) are on the links (arrows), while on DOS/Windows names are on nodes (boxes).
If you want to explore a tag-based system, take a look at https://www.tagspaces.org/