home.social

#devenv — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #devenv, aggregated by home.social.

  1. So, I gave #devenv a try.

    I'm used to work with #nix #flakes but I have to admin the devenv.nix file is less cluttered which lead to a better UX. But this comes at the cost of an extra devenv.yaml file. Why not, not a fan, but it works.

    But, while #devenv configs are composable locally, they can't import a remote config as #flake does.

    Also, `devenv shell` breaks my #tmux / #nvim setup where my #flake works like a charm.
    So, yeah, I'll keep my #flake for now.
    At work and at home.

    CC @Ilygad

  2. So, I gave #devenv a try.

    I'm used to work with #nix #flakes but I have to admin the devenv.nix file is less cluttered which lead to a better UX. But this comes at the cost of an extra devenv.yaml file. Why not, not a fan, but it works.

    But, while #devenv configs are composable locally, they can't import a remote config as #flake does.

    Also, `devenv shell` breaks my #tmux / #nvim setup where my #flake works like a charm.
    So, yeah, I'll keep my #flake for now.
    At work and at home.

    CC @Ilygad

  3. So, I gave #devenv a try.

    I'm used to work with #nix #flakes but I have to admin the devenv.nix file is less cluttered which lead to a better UX. But this comes at the cost of an extra devenv.yaml file. Why not, not a fan, but it works.

    But, while #devenv configs are composable locally, they can't import a remote config as #flake does.

    Also, `devenv shell` breaks my #tmux / #nvim setup where my #flake works like a charm.
    So, yeah, I'll keep my #flake for now.
    At work and at home.

    CC @Ilygad

  4. So, I gave #devenv a try.

    I'm used to work with #nix #flakes but I have to admin the devenv.nix file is less cluttered which lead to a better UX. But this comes at the cost of an extra devenv.yaml file. Why not, not a fan, but it works.

    But, while #devenv configs are composable locally, they can't import a remote config as #flake does.

    Also, `devenv shell` breaks my #tmux / #nvim setup where my #flake works like a charm.
    So, yeah, I'll keep my #flake for now.
    At work and at home.

    CC @Ilygad

  5. So, I gave #devenv a try.

    I'm used to work with #nix #flakes but I have to admin the devenv.nix file is less cluttered which lead to a better UX. But this comes at the cost of an extra devenv.yaml file. Why not, not a fan, but it works.

    But, while #devenv configs are composable locally, they can't import a remote config as #flake does.

    Also, `devenv shell` breaks my #tmux / #nvim setup where my #flake works like a charm.
    So, yeah, I'll keep my #flake for now.
    At work and at home.

    CC @Ilygad

  6. I set up my first devenv for my next project today after upgrading to macOS Tahoe. Pretty smooth. On both fronts, actually. Also back on a Plone project for the first time in a while.

  7. I set up my first devenv for my next project today after upgrading to macOS Tahoe. Pretty smooth. On both fronts, actually. Also back on a Plone project for the first time in a while.

    #devenv #nix #Plone

  8. Was just checking out some tvix talks, the tvix-store is certainly attractive with even the replit blog mentioning about 90% storage reduction in cache storage. Even devenv switched to tvix.

    But I couldn't see any docs on how can I start using it in my nixos or atleast for nix shells, etc

    Am I missing out something or any views on this would help me
    #nix #tvix #cache #devenv #replit

  9. Was just checking out some tvix talks, the tvix-store is certainly attractive with even the replit blog mentioning about 90% storage reduction in cache storage. Even devenv switched to tvix.

    But I couldn't see any docs on how can I start using it in my nixos or atleast for nix shells, etc

    Am I missing out something or any views on this would help me
    #nix #tvix #cache #devenv #replit

  10. Really sad the that #devenv 2.0 version got so much worse. :( I get port-shifts over and over again when restarting it and the new process-manager overview is hardly usable for me. Wondering if I should go back to 1.9 or if there even is a fork?

  11. Really sad the that #devenv 2.0 version got so much worse. :( I get port-shifts over and over again when restarting it and the new process-manager overview is hardly usable for me. Wondering if I should go back to 1.9 or if there even is a fork?

  12. #Microsoft #VisualStudio 2026 #DevEnv
    fails to remote-attach, and crashes with 0xC0000005. Great job.

  13. #Microsoft #VisualStudio 2026 #DevEnv
    fails to remote-attach, and crashes with 0xC0000005. Great job.

  14. 2 is out and it is impressive! 😁 Great work team. Going to ride through in some personal projects to test out.

    I been moving to flake parts all my things, but still. Would like these dev shell benefits. 😎

    devenv.sh/blog/2026/03/05/deve

  15. #Devenv 2 is out and it is impressive! 😁 Great work team. Going to ride through in some personal projects to test out.

    I been moving to flake parts all my things, but still. Would like these dev shell benefits. 😎

    devenv.sh/blog/2026/03/05/deve

  16. Just published a short article on my new project Karapace — a tool to make development environments deterministic, reproducible, and identity-first. Traditional container workflows often leave too much implicit, leading to “it works on my machine” problems. Karapace fixes that with content-addressed environments and reproducible lockfiles.

    Read more 👉 marcoallegretti.me/blog/karapa

    #karapace #rust #devenv #containers #linux

  17. @upmultimedia you might want to check out #Nix and/or #devenv, both of which allow you to get reproducible and isolated environments. The learning curve might be a bit steep but the experience is way better than what you get with containers.

  18. @upmultimedia you might want to check out #Nix and/or #devenv, both of which allow you to get reproducible and isolated environments. The learning curve might be a bit steep but the experience is way better than what you get with containers.

  19. Started my new pet project on devenv.sh. Lord, what a relieve compared to any Docker/Vagrant/Kubernetes dev setup I've seen, yet. #devenv

  20. Started my new pet project on devenv.sh. Lord, what a relieve compared to any Docker/Vagrant/Kubernetes dev setup I've seen, yet. #devenv

  21. #TIL about one of the most useful tools for #nix and #nixos - github.com/samestep/npc

    It is basically a git bisect but for nix channels. It also has great flake support. Just run npc bisect until you find the #nixpkgs version that works and it will automatically fix it in your flake.lock.

    The issue for me was #devenv package being broken in the latest nixpkgs-stable release (github.com/NixOS/nixpkgs/issue). It turns out ghidra build results are not used to determine the package status and the possibility to commit the new version to master branch.

    I think this tool is a game changer, especially if you use nixpkgs-unstable

    #npc #nixpkgs

  22. Profile control in is kind of outstanding. I have this very problem with monorepo dev work. Not all the time you need to load everything under the sun. 😅

    Going to see how to fit on these very repos. 😁

    devenv.sh/blog/2025/09/17/deve

  23. Profile control in #devenv is kind of outstanding. I have this very problem with monorepo dev work. Not all the time you need to load everything under the sun. 😅

    Going to see how to fit on these very repos. 😁

    devenv.sh/blog/2025/09/17/deve

  24. Sehr schöner Abend bei einer tollen Location mit Leuten auf die ich mich gefreut habe und tollen Vorträgen. Danke Euch @sparsick , Andreas Malerz, @sormuras, Stephan Kaps und der cronn GmbH.

    #JUG #JUGBonn #Java #KRITIS #DevEnv

  25. Sehr schöner Abend bei einer tollen Location mit Leuten auf die ich mich gefreut habe und tollen Vorträgen. Danke Euch @sparsick , Andreas Malerz, @sormuras, Stephan Kaps und der cronn GmbH.

    #JUG #JUGBonn #Java #KRITIS #DevEnv

  26. I'm still confused about the versioning in #devenv: nixos unstable has bun at 1.2.19. Nixos 25.05 has it on 1.2.13. Devenv's fork of nixpkgs? 1.2.10.

    I suppose that the fork is solving _some_ problems, but I cant' remember a time when I haven't stumbled on a weird package issue only because devenv is lagging behind so hard and I forgot to reset it to upstream immediately after creation.

  27. I'm still confused about the versioning in #devenv: nixos unstable has bun at 1.2.19. Nixos 25.05 has it on 1.2.13. Devenv's fork of nixpkgs? 1.2.10.

    I suppose that the fork is solving _some_ problems, but I cant' remember a time when I haven't stumbled on a weird package issue only because devenv is lagging behind so hard and I forgot to reset it to upstream immediately after creation.

  28. Ohai #nixOS und #developer Bubble! Was bevorzugt ihr: #devenv (devenv.sh/) oder #devbox (jetify.com/devbox/)?

    Meine und eure Gedanken dazu: 👇ich freu' mich auf eure Replies!

    Bitte :BoostOK: für mehr Input 😊

  29. Some more prodding (I should really prod more before ranting...) uncovered that emacs can't load my #devenv's generated direnv. Fantastic.

    At least I have some idea about what's broken, now.

  30. Some more prodding (I should really prod more before ranting...) uncovered that emacs can't load my #devenv's generated direnv. Fantastic.

    At least I have some idea about what's broken, now.

  31. Not really surprising though I guess, its the corporate way of doing things.
    You do something shady, get called out, apologize in an hand wavy, noncommittal kind of way, promise to do better, and then instead of doing anything wait until it blows over and quietly bring the thing back.
    It's really kind of a classic.

    #nix #nixos #devenv

  32. Not really surprising though I guess, its the corporate way of doing things.
    You do something shady, get called out, apologize in an hand wavy, noncommittal kind of way, promise to do better, and then instead of doing anything wait until it blows over and quietly bring the thing back.
    It's really kind of a classic.

    #nix #nixos #devenv

  33. I guess its totally cool that #devenv 1.5 was pushed into #nixpkgs, bringing back both telemetry and source code upload for AI training, and neither @domenkozar's blog post nor the release announcement mentions anything about that, right?

    #nix #nixos

  34. I guess its totally cool that #devenv 1.5 was pushed into #nixpkgs, bringing back both telemetry and source code upload for AI training, and neither @domenkozar's blog post nor the release announcement mentions anything about that, right?

    #nix #nixos

  35. I’ve just been told about #Devbox and #devenv. Are they as cool as they claim to be? Looks like they both bring everything I could’ve wanted for my development environments.
    (Powered by #Nix, btw.)

    jetify.com/devbox
    devenv.sh

  36. I’ve just been told about #Devbox and #devenv. Are they as cool as they claim to be? Looks like they both bring everything I could’ve wanted for my development environments.
    (Powered by #Nix, btw.)

    jetify.com/devbox
    devenv.sh

  37. I though it had been a while without any #NixOS drama, but of course the universe provides.

    Guess what, telemetry in #devenv is coming back. Again, it's Opt-Out, not Opt-In.
    The difference: this time that work is sponsored by the NixOS Foundation.

    github.com/cachix/devenv/pull/

    oceansprint.org/reports/2025/

    #nix #nixpkgs

    Brought to you by @domenkozar of course.

  38. I though it had been a while without any #NixOS drama, but of course the universe provides.

    Guess what, telemetry in #devenv is coming back. Again, it's Opt-Out, not Opt-In.
    The difference: this time that work is sponsored by the NixOS Foundation.

    github.com/cachix/devenv/pull/

    oceansprint.org/reports/2025/

    #nix #nixpkgs

    Brought to you by @domenkozar of course.

  39. If I ever recommended devenv to you: I'm sorry!
    The new version (1.4) has a function which will silently upload your entire repo you call it on to their servers to do whatever with it – they call it telemetry, not exfiltration.
    If you're on nixos stable you didn't get 1.4 yet, so you can fix your machine before it gets impacted.

    My new recommendation is to uninstall devenv, delete your devenv configs, use anything else.
    They are saying they will roll that change back, but the tool is burned, there's no recovering from this.

    #devenv #devenvsh

  40. @domenkozar
    Tell you what: you publish a blog post on devenv.sh owning up to what happened, and I'll apologize for assuming malicious intent.

    @Pol @neo @cafkafk @roberth @jfredett @oliverwiegers

    #nix #nixos #devenv

  41. CW: devenv generate uploads repo contents

    The #devenv CLI does not do informed consent and neither `devenv.sh` nor `devenv.new` have a privacy policy or will tell you who runs the service and who it shares its data with.

    In #nixpkgs the package was bumped to 1.4.0 after which a contributor immediately sent a follow-up PR¹ to enable `DO_NOT_TRACK=1` when wrapping the devenv binary.

    This was promptly reverted² by the author of devenv.

    🧵2/n

    [1] github.com/NixOS/nixpkgs/pull/
    [2] github.com/NixOS/nixpkgs/pull/

  42. CW: devenv generate uploads repo contents

    If you're using #devenv for your projects, please note that the new `generate` command in 1.4.0 uses your repository content.

    It tars up all files it can find through `git ls-files -z`³ and exfiltrates them to the service.

    It handles `DO_NOT_TRACK=`¹ by sending that intent along² as a query string, so now you need to trust the service to not keep data.

    🧵 1/n

    [1] github.com/cachix/devenv/blob/
    [2] github.com/cachix/devenv/blob/
    [3] github.com/cachix/devenv/blob/

  43. @jfredett @oliverwiegers .... and reverted by the author, who apparently has commit rights and does not seem to agree with community PR workflow.

    So we now have commercial actors in #nixpkgs who can just push their own commercial agenda be decree.

    #nix #nixos #devenv