If you're at #KubeCon today (or the rest of the week?) do go say hi to the #CUE folks I help write their open-source docs (https://cuelang.org/docs) 'cos I *really* want the awesome tech to succeed!

If you're a #SysAdmin or #DevOps in #YAML config hell go and have a chat with them - next to the CNCF corner store at stall S761

You do not like #xml.

You are being hostage and feel empathy for your jailer.

- It is more machine than human readable.

- It is a pain to convert to and from #json, #yaml, #toml because of loose structure rules.

- It is unfortunately everywhere it shouldn't be.

I have tried them all.
And I finally stick with #sozu + #letsencrypt!

It's a webserver/proxy with:

- hot reload
- builtin metrics
- minimal #toml configuration

You should give it a shot.
It is fairly quick to configure and get running.

#webdev #nginx #caddy
https://github.com/sozu-proxy/sozu

Here my quick build of a bash toml parser based on kwmiebach's (https://github.com/kwmiebach) version on github. Thanks kwmiebach!
https://codeberg.org/oxo/tool/src/branch/main/toml-read

The order of arguments (file, section key) is irrelevant. Data is aggregated if no key or section is given.

My idea is to integrate it with my paasword manager passr. Then my password files can be toml format.

Have a nice weekend!

#helix vs #neovim. spot the differences!

the main one isn't really visible, though: helix has a built-in #treesitter, and it does a great job at highlighting #rust out of the box, with zero configuration and dependencies!

this way, i don't have 20 plugins in #lua and/or #vimscript running in the background and autoupdating from #github - awesome! config is plain #toml - no need to write it in turing-complete languages which i only know poorly

shout out @bobulous https://www.bobulous.org.uk/coding/Helix-crib-sheet.html

Run pipelines in the terminal.

#pipelight is a cli/engine that runs pipelines in the terminal.(pssst: it's #foss and #rust )

It has json AND pretty tree outputs so you can inspect every process outputs fairly quickly.

Supports #yaml, #toml, #hcl, #javascript and some other languages.

#sysadmin #devops #cicd #developers
Every buzz word are thereso you don't miss it, thk me later

https://github.com/pipelight/pipelight

#JSONCrack: Visualize Complex Data with Interactive Graphs

• #JSONCrack transforms #JSON, #YAML, #CSV, #XML & #TOML into navigable interactive graphs with dark/light modes

If you are into TOML, support for Scala 3 derivation was recently added to this library. I personally will stick with HOCON. By the way, does anyone use SConfig instead of the original Java implementation from TypeSafe? #scala #toml #hocon https://github.com/indoorvivants/toml-scala

Started a #Perl program to parse #TOML file, initially crudely. Then thought should use existing software in form of a module to extract more than the rudimentary data.

So far #FreeBSD (Perl) packages are only for TOML v.0.4.0; missing is "TOML::Tiny" https://metacpan.org/pod/TOML::Tiny to parse TOML v1.0.0.

OTOH, #Python "tomli" package is available to parse TOML v1.0.0. See also "tomllib"

I would rather switch programming languages to have system packages as the updates are easier

Would anyone who knows #Traefik and #YAML or #TOML be willing to help me out? I'm trying to get Traefik set up with my new domain but running into trouble, and I'm not sure what I'm doing wrong. I can send you my traefik.toml and dashboard.yml files.
#SelfHosted #SelfHosting #Linux #Tech #Technology
@selfhost @selfhosting @selfhosted

Random #Python moment:

print(foo) says "None"
foo == None returns false
foo is None returns false

Lots and lots of head-scratching ensues

OH RIGHT. I FORGOT. I had specified that in config file, 'None' (string) is the way to specify no value. Because #TOML doesn't have a null type.

As _why said, "one too many nulls today"

Всё про конфиги

Материалы лекции про конфигурационные файлы — все основные аспекты написания и использования конфигов для самых маленьких, примеры кода на python. Узнать страшную правду

https://habr.com/ru/articles/866468/

Introduction to #TOML and #Taplo https://pin.it/3CUezm6gq via
@pinterest

I am really curious what will happen if I put captured network traffic into toml format instead of csv that I usually use. #data #format #toml

Using TOML for config and using the results to construct pydantic dataclasses means I get type-validation and required-keys-validation "for free". This is quite nice.

People: I've been doing TOML wrong!

Not this:

foo = { thing = "that goes off the side", of = "the screen", because = "you are not allowed line breaks", in = "inline tables"}

but this:

foo.thing = "that goes off the side"
foo.of = "the screen"
foo.because = "you are not allowed line breaks"
foo.in = "inline tables"

I thought I needed whole TOML docs to be allowed inside {} (and that would be nice!) but I didn't because I can do this instead.

Kiedy przypadkowe projekty używające narzędzia do formatowania plików #PyProjectToml, od pewnej osoby z opiniami, i nagle pliki `pyproject.toml` tych wszystkich projektów zaczynają wyglądać, jakby ktoś je wysrał, bo rzeczona osoba zmieniła zdanie, i stwierdziła, że klucze z kropkami dla tabelek #TOML nie są fajne, i lepiej wszystkie wartości w upchnąć w nadrzędnych tabelach. Czy muszę dodawać, że to zupełnie inaczej, niż stosuje się w przykładach dla każdego jednego systemu budowania #PEP517?

Kilka przykładów projektów, w których to nastąpiło (często za sprawą pre-commit):

https://github.com/pypa/virtualenv/commit/7cbed79924b6b6d953ca9ecf40de23a7d3486f57#diff-50c86b7ed8ac2cf95bd48334961bf0530cdc77b5a56f852c5c61b89d735fd711
https://github.com/django-commons/django-debug-toolbar/commit/2990290d43618df5eab357f2a36363186d51d5a8#diff-50c86b7ed8ac2cf95bd48334961bf0530cdc77b5a56f852c5c61b89d735fd711
https://github.com/pytest-dev/pytest/commit/5d5c9dc85850f64621190e62bd20d4b190bdbdb6#diff-50c86b7ed8ac2cf95bd48334961bf0530cdc77b5a56f852c5c61b89d735fd711
https://github.com/prettytable/prettytable/commit/88bebdac122b82af255656513080bdd2c90098d9#diff-50c86b7ed8ac2cf95bd48334961bf0530cdc77b5a56f852c5c61b89d735fd711
https://github.com/python-humanize/humanize/commit/aa3a94e011a795a0551717c5a78a566bc2672390#diff-50c86b7ed8ac2cf95bd48334961bf0530cdc77b5a56f852c5c61b89d735fd711
https://github.com/termcolor/termcolor/commit/9e35c66ab7ad48a33d5c2829dbee02382aa716e5#diff-50c86b7ed8ac2cf95bd48334961bf0530cdc77b5a56f852c5c61b89d735fd711

When random projects use a certain #PyProjectToml formatter from a certain opinionated upstream, and now all projects suddenly have their `pyproject.toml` files rewritten to look like shit, because opinionated upstream changed their mind, and decided that dotted #TOML table keys are no cool and it's better to inline everything into top-level tables. Which — I should point out — is against the style used in examples of every single #PEP517 build system out there.

Just a few examples where it happened (often via pre-commit hooks):

https://github.com/pypa/virtualenv/commit/7cbed79924b6b6d953ca9ecf40de23a7d3486f57#diff-50c86b7ed8ac2cf95bd48334961bf0530cdc77b5a56f852c5c61b89d735fd711
https://github.com/django-commons/django-debug-toolbar/commit/2990290d43618df5eab357f2a36363186d51d5a8#diff-50c86b7ed8ac2cf95bd48334961bf0530cdc77b5a56f852c5c61b89d735fd711
https://github.com/pytest-dev/pytest/commit/5d5c9dc85850f64621190e62bd20d4b190bdbdb6#diff-50c86b7ed8ac2cf95bd48334961bf0530cdc77b5a56f852c5c61b89d735fd711
https://github.com/prettytable/prettytable/commit/88bebdac122b82af255656513080bdd2c90098d9#diff-50c86b7ed8ac2cf95bd48334961bf0530cdc77b5a56f852c5c61b89d735fd711
https://github.com/python-humanize/humanize/commit/aa3a94e011a795a0551717c5a78a566bc2672390#diff-50c86b7ed8ac2cf95bd48334961bf0530cdc77b5a56f852c5c61b89d735fd711
https://github.com/termcolor/termcolor/commit/9e35c66ab7ad48a33d5c2829dbee02382aa716e5#diff-50c86b7ed8ac2cf95bd48334961bf0530cdc77b5a56f852c5c61b89d735fd711