So is .toml the preferred choice over .yaml now?
So is .toml the preferred choice over .yaml now?
I was searching for a "from_toml" Ansible filter when, all of the sudden, a wild repository appeared: https://github.com/sivel/toiletwater
Here is the original issue on github https://github.com/ansible/ansible/issues/69120
Curious collection name. It even has a logo
I'm at an annual participants' meeting of @revspace
The current "slides" are a #TOML outline list shown in #vim at 25x80 on a large screen TV.
Everything is on brand. #DeathByPowerPoint #DeathToPowerPoint #HackerSpace
`cargo-sort`, https://crates.io/crates/cargo-sort.
Check if tables and items in a `.toml` file are lexically sorted.
Pretty handy to get nice `Cargo.toml` files for example!
The CUE project has just released v0.13.0 - the culmination of a year's worth of work to enable the new, faster, better, (stronger? harder?) evaluator by default!
https://github.com/cue-lang/cue/releases/tag/v0.13.0
The release also packs in loads of new features, such as support for absolute module packages, dozens of JSON Schema improvements, and a new experimental XML encoding.
Poetry is a Python tool for dependency management and packaging, simplifying how you handle the libraries your project needs and how you build and distribute your project. It replaces traditional tools like requirements.txt, setup.py, and MANIFEST.in with a more streamlined approach using a pyproject.toml file.
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.
#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
#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"
There is a flavour of JSON that supports comments (JSONC) but of course it's non-standard and not supported in most JSON contexts. And it exists solely because of some programs insisting on keeping their configurations in JSON format, and config files *always* need comments...
I wasn't originally in favour of the choice of TOML (DOS/Windows ".ini" syntax on steroids) for the Python project config/metadata file, thinking YAML would have been better, but I've come around. YAML is still primarily suited for programs to write and parse. The fact that programmers can also write and parse it is useful, but doesn't mean it's suited for use as a general configuration file format to be used by normal people.
At least TOML they have a (small) chance of finding not too frustrating.
I suppose you could look at TOML (or even plain .ini) syntax for your unrelated thing, depending on its requirements.
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.