The hard drive is full. Surely I have lots of stuff I don’t really need and could delete. Let’s see…

Nop, can’t delete
Nop
Nop
Nop, I need this
Nop
Nop
Nop, I don’t want to delete that

Oh, I need a bigger drive. This one is too small, that’s the problem!

[Repeat every X months]

⤋ Read More
In-reply-to » Yeah, the lack of comments makes regular JSON not a good configuration format in my view. Also, putting all keys in quotes and the use of commas is annoying. The big upside is that's in lots of standard libraries.

I can query the configurations a few different ways. i can request the specific name foo.bar or a glob like foo.* or trace the hierarchy trace:some.deep.name.space which will give me the namespaces some, some.deep, some.deep.name, and some.deep.name.space. These can be combined.

⤋ Read More
In-reply-to » Yeah, the lack of comments makes regular JSON not a good configuration format in my view. Also, putting all keys in quotes and the use of commas is annoying. The big upside is that's in lots of standard libraries.

@lyse@lyse.isobeef.org its a hierarchy key value format. I designed it for the network peering tools i use.. I can grant access to different parts of the tree to other users.. kinda like directory permissions. a basic example of the format is:

@namespace
# multi
# line
# comment
root :value

# example space comment
@namespace.name space-tag 

# attribute comments
attribute attr-tag  :value for attribute

# attribute with multiple 
# lines of values
foo :bar
      :bin
      :baz

repeated :value1
repeated :value2

each @ starts the definition of a namespace kinda like [name] in ini format. It can have comments that show up before. then each attribute is key :value and can have their own # comment lines.
Values can be multi line.. and also repeated..

the namespaces and values can also have little meta data tags added to them.

the service can define webhooks/mqtt topics to be notified when the configs are updated. That way it can deploy the changes out when they are updated.

⤋ Read More
In-reply-to » @lyse Lack of comments are definitely a shortcoming of JSON. I don't like TOML because it lets you have nested categories ([foo] [foo.bar] [foo.baz]) and it just feels confusing to me, even with indentation. Simple INI files are okay.

@mckinley@twtxt.net Don’t forget the syntax for arrays of sets [[foo.bars]] [[foo.bars]] [[foo.bars]]

⤋ Read More

Starting (again) to work on something very old, I discovered it modulates up by a halfstep twice. Up, up, done. Maybe I can work in some extremely slow contrary motion, too.

⤋ Read More
In-reply-to » Question of the day: What configuration file formats do you all like and use?

@lyse@lyse.isobeef.org Regarding YAML’s readability, I miss the - for list items constantly when reading YAML files. I’ll get confused because I think I’m not in a list or I’m in the previous list item, then I have to go back. List items are all on the same indentation column and one tiny character is the only thing defining a new one. I don’t know if others have this problem.

⤋ Read More
In-reply-to » @lyse Lack of comments are definitely a shortcoming of JSON. I don't like TOML because it lets you have nested categories ([foo] [foo.bar] [foo.baz]) and it just feels confusing to me, even with indentation. Simple INI files are okay.

I spent hours creating a perfect Prosody config for my most recent XMPP server attempt (about 2-3 years ago now) and I lost that file because I deleted the VPS. That was the only important file on there and I just didn’t think of it when I deleted it. I didn’t have a single backup, not even an old copy I scped back to my PC for editing.

I hope I won’t make that mistake again but I wouldn’t be surprised if I did.

⤋ Read More
In-reply-to » Question of the day: What configuration file formats do you all like and use?

@lyse@lyse.isobeef.org Lack of comments are definitely a shortcoming of JSON. I don’t like TOML because it lets you have nested categories ([foo] [foo.bar] [foo.baz]) and it just feels confusing to me, even with indentation. Simple INI files are okay.

The Prosody XMPP server’s configuration file is just a Lua script because Prosody is written in Lua, and that’s excellent.

⤋ Read More
In-reply-to » Question of the day: What configuration file formats do you all like and use?

Yeah, the lack of comments makes regular JSON not a good configuration format in my view. Also, putting all keys in quotes and the use of commas is annoying. The big upside is that’s in lots of standard libraries.

I think the appeal with YAML is that is has comments, is kind of easy to write and read and also provides unlimited nesting levels. But it has all its drawbacks, no question. Forbidding tabs, thousands of different string flavors, having so many boolean options (poor Norwegians) etc. I use it, but I don’t particularly enjoy it.

Among simple key value pairs, I like INI files, but with # for comments, not ;. I never used TOML, read up on it yesteray before writing this question, but it looks a bit weird and has some strange rules. I guess I have to give it a try one day.

And yes, as mentioned by several of you, it always depends on the complexity of the configuration at hand.

I’m developing something for the scouts at the moment with rather simple requirements on the config. Currently, there are just four settings. Even INI would be overkill with its section. I selected JSON for now, because that’s readily available with Go’s std lib. But I do not like it.

Btw. what’s your own config format, @xuu@txt.sour.is?

⤋ Read More

OK mas

Se uma partícula ⚛️ estiver a circular a uma fracção da velocidade da luz 🔦🏃assim altos speeds mesmo 🏃🏃

E o tempo fica todo relativizado 📈 todo fodido 💩

E a partícula ⚰️morre ☠️!!!!!!!!

Quando é que calha a ⛪ missa 🙏 de sétimo dia?? 🤔

⤋ Read More
In-reply-to » yeah, where and how can we sign up?

Organization eligibility

  • Must run an active open source or free software project.
  • Must have produced and released software under an OSI approved license.
  • Must not be based in a country currently embargoed by the United States.

Sadly the application period is over, but we could register the project for next year.
https://summerofcode.withgoogle.com/how-it-works
https://www.youtube.com/watch?v=L4JNz6zWzLs

⤋ Read More
In-reply-to » Question of the day: What configuration file formats do you all like and use?

For Python, env files with dotenv.
For JS, usually JSONP or a config.js
For PHP a config.php with an array usually works
For C#, I try to avoid the ugly native XML, but it’s what most of the team use…

For most I have a .env.sample in the repo, and we ignore .env or config* to avoid storing credentials.

⤋ Read More