Plop.js is awesome. I wanted it on non-node projects. But I'd need to list node, package.json, package.lock and have node_modules themselves in the project folder, right? Not any more.
Now it's a development shell dependency. Keeping Node itself outside of the project. Just the plopfile, and the templates need to be present.
Got my first development environment (Jekyll website) running in NixOS on my Framework laptop using devenv. That makes this my first successful dev environment in nix. :) Nice work @domenkozar!
Man, the longer I have :nixos: #NixOS and :manjaro: #Manjaro running in parallel, the more annoyed I am by the :archlinux: #ArchLinux way, e.g.:
· Python update ⇒ all python-based #AUR packages must be rebuilt. #pipx-installed packages also need reinstallation.
· separation between distro repos and AUR is anoying. 'yay -Syu' (or whatever) never really works in one go (be it some stupid sudo prompt later)
· so many AUR packages don't build reliably or at all.
...
In :nixos: #NixOS, you have a higher upfront effort to configure your system and package your own things, but the huge difference to other traditional distros is that this is a ONE-TIME effort: Once you have a NixOS package that does the job (even barely), you can pin it and keep using it eternally - with all its dependencies pinned as well. No moving parts anymore.
@nobodyinperson Completely agree! When I used Ubuntu and needed to tweak something I was always worried that I would forget what I'd done and be unable to fix it again in the future. With #NixOS it's written down and commented, and I can deploy the same config over and over again 😁
Pre-warning to my followers: I'm going to leave #reddit for good and I'm blogging about the reasons - mostly because reddit management gone crazy (latest: my #firefox isn't working any more for reddit) & also because of https://karl-voit.at/2020/10/23/avoid-web-forums/
Wrote a post on how to do reasonable pinning for non-flake configs using a simple shell script, npins, and nixos-rebuild. I also talk about how tools like nixos-rebuild and nix-channel are skeletons in our closet that we need to actually replace and deprecate as a community, to bring people up to modern practices.
I have been working on something, which is not totally ready.
Most of the deployment tools in the #NixOS ecosystem are tailored to... NixOS. NixOS can run in a bunch of places, but not easily on 256MB RAM devices and 32MB disk.
anyone have a good resource for converting a binary to a #nixos service? I think i got pretty far with @readeckhttps://readeck.org/en/docs/deploy but i have no clue how to handle the /etc/ files it claims it needs and keep getting vague 203 errors.