<fadenb>
This link is a screenshot of some Google report on the nixos.wiki domain
<gchristensen>
nice
<gchristensen>
I was worried it was going to be the bad kind of report
<gchristensen>
all 104 searches for "nixos zfs" is me (kidding)
tilpner_ has joined #nixos-wiki
tilpner has quit [Ping timeout: 276 seconds]
tilpner_ is now known as tilpner
<makefu>
so many clicks from the US, however i do not feel that the US community is much involved in the development process, however i may be wrong
<azazel>
and so many "nixos docker"!
<makefu>
that is quite sad actually
<ddima>
well, one can wonder about the intention. one interpretation could be "how can I try out nixos in docker" or sth.
<makefu>
true
<ddima>
but realistically, if you're not full-on nix, you're gonna be dealing with a lot of docker based things at work, so maybe thats one of the first things people stumble over
<makefu>
using nixOS as host system is just the entry drug, soon you will want the full nixos experience
<fadenb>
heh, if it were that simple :P
<fadenb>
I am on NixOS for all my devices for several years but getting it into production at work is a whole different story
<fadenb>
we have a few nixos systems (internally and with customers) but we often lack the time to e.g. write new modules to manage applications that do not exist yet so we have to fall back to docker
<ddima>
well, also with the high prevalence and popularity of k8s, that's how it's gonna be (well, or podman or similar)
<ddima>
(imho "nah, seems redundant" is a valid judgement too for such a thing)
<azazel>
ddima: I've read it unitl the "nix-shell" section (excluded). It's nice, thanks for it! Maybe I would prefer an extended "common nix errors" with more than just one example
<azazel>
but I never used nixfmt
<ddima>
thats a good point, Im just not sure off the top of my head how to collect such a list
<ddima>
the idea was to actually have "easily useable" code examples, so one would have to construct a few cases that one perceives as common. if you have some off the top of your head, let me know and I will try to construct some and work them in. at the same time, one should ofc be mindful of the scope. that's also why Im kinda curious which of the existing doc sources could be a good home for some content
<ddima>
like that, to work that into some existing structure and then see where other things could fit.
<ddima>
it could ofc also just live on its own, but I think right now, with all the doc improvement discussions, is probably a good chance to consolidate some things.