home.social

#devbox — Public Fediverse posts

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

  1. Not entirely shure where I’m taking a wrong turn here..

    • I’m provisioning a throw-away server using an emphemeral key
    • the server is tagged as “server” and “ephemeral”
    • I can see it as ephemeral in my Tailscale admin panel
    • I’m running tailscaled with “—state=mem”
    • I’m even doing an explicit “tailscale logout” on shutdown

    Yet.. the instance sticks around in my Tailscale control panel for hours if not longer and blocks the hostname during that time.

    Anyone in the same situation?

    #tailscale #ephemeral #devbox #help

  2. Not entirely shure where I’m taking a wrong turn here..

    • I’m provisioning a throw-away server using an emphemeral key
    • the server is tagged as “server” and “ephemeral”
    • I can see it as ephemeral in my Tailscale admin panel
    • I’m running tailscaled with “—state=mem”
    • I’m even doing an explicit “tailscale logout” on shutdown

    Yet.. the instance sticks around in my Tailscale control panel for hours if not longer and blocks the hostname during that time.

    Anyone in the same situation?

    #tailscale #ephemeral #devbox #help

  3. Not entirely shure where I’m taking a wrong turn here..

    • I’m provisioning a throw-away server using an emphemeral key
    • the server is tagged as “server” and “ephemeral”
    • I can see it as ephemeral in my Tailscale admin panel
    • I’m running tailscaled with “—state=mem”
    • I’m even doing an explicit “tailscale logout” on shutdown

    Yet.. the instance sticks around in my Tailscale control panel for hours if not longer and blocks the hostname during that time.

    Anyone in the same situation?

    #tailscale #ephemeral #devbox #help

  4. Not entirely shure where I’m taking a wrong turn here..

    • I’m provisioning a throw-away server using an emphemeral key
    • the server is tagged as “server” and “ephemeral”
    • I can see it as ephemeral in my Tailscale admin panel
    • I’m running tailscaled with “—state=mem”
    • I’m even doing an explicit “tailscale logout” on shutdown

    Yet.. the instance sticks around in my Tailscale control panel for hours if not longer and blocks the hostname during that time.

    Anyone in the same situation?

    #tailscale #ephemeral #devbox #help

  5. Not entirely shure where I’m taking a wrong turn here..

    • I’m provisioning a throw-away server using an emphemeral key
    • the server is tagged as “server” and “ephemeral”
    • I can see it as ephemeral in my Tailscale admin panel
    • I’m running tailscaled with “—state=mem”
    • I’m even doing an explicit “tailscale logout” on shutdown

    Yet.. the instance sticks around in my Tailscale control panel for hours if not longer and blocks the hostname during that time.

    Anyone in the same situation?

    #tailscale #ephemeral #devbox #help

  6. 🚀✨ Behold, the magical Devbox! A miraculous tool that promises to wrap your #development nightmares in a shiny #Docker box 🎁, just like every other tool that came before it. But hey, at least it'll keep your laptop from melting while you try to remember yet another command syntax. 🔥🙃
    devbox.ar0.eu/ #Devbox #Tools #SoftwareEngineering #TechHumor #HackerNews #ngated

  7. 🚀✨ Behold, the magical Devbox! A miraculous tool that promises to wrap your #development nightmares in a shiny #Docker box 🎁, just like every other tool that came before it. But hey, at least it'll keep your laptop from melting while you try to remember yet another command syntax. 🔥🙃
    devbox.ar0.eu/ #Devbox #Tools #SoftwareEngineering #TechHumor #HackerNews #ngated

  8. 🚀✨ Behold, the magical Devbox! A miraculous tool that promises to wrap your #development nightmares in a shiny #Docker box 🎁, just like every other tool that came before it. But hey, at least it'll keep your laptop from melting while you try to remember yet another command syntax. 🔥🙃
    devbox.ar0.eu/ #Devbox #Tools #SoftwareEngineering #TechHumor #HackerNews #ngated

  9. 🚀✨ Behold, the magical Devbox! A miraculous tool that promises to wrap your #development nightmares in a shiny #Docker box 🎁, just like every other tool that came before it. But hey, at least it'll keep your laptop from melting while you try to remember yet another command syntax. 🔥🙃
    devbox.ar0.eu/ #Devbox #Tools #SoftwareEngineering #TechHumor #HackerNews #ngated

  10. TIL: in #devbox (#nix), packages have different "outputs". So when my #rust compilation fails, because it cannot link with curl, it is not enough to run

    devbox add curl

    because that only adds the "bin" and "man" outputs. And, even though an output named "lib" is sometimes available, most of the packages don't have it :(

    The last output is called "out", where all the other stuff goes in. So the rust linker needs

    devbox add curl -o out

    Logical, no?

  11. TIL: in #devbox (#nix), packages have different "outputs". So when my #rust compilation fails, because it cannot link with curl, it is not enough to run

    devbox add curl

    because that only adds the "bin" and "man" outputs. And, even though an output named "lib" is sometimes available, most of the packages don't have it :(

    The last output is called "out", where all the other stuff goes in. So the rust linker needs

    devbox add curl -o out

    Logical, no?

  12. TIL: in #devbox (#nix), packages have different "outputs". So when my #rust compilation fails, because it cannot link with curl, it is not enough to run

    devbox add curl

    because that only adds the "bin" and "man" outputs. And, even though an output named "lib" is sometimes available, most of the packages don't have it :(

    The last output is called "out", where all the other stuff goes in. So the rust linker needs

    devbox add curl -o out

    Logical, no?

  13. TIL: in #devbox (#nix), packages have different "outputs". So when my #rust compilation fails, because it cannot link with curl, it is not enough to run

    devbox add curl

    because that only adds the "bin" and "man" outputs. And, even though an output named "lib" is sometimes available, most of the packages don't have it :(

    The last output is called "out", where all the other stuff goes in. So the rust linker needs

    devbox add curl -o out

    Logical, no?

  14. 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 😊

  15. 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 😊

  16. 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 😊

  17. 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 😊

  18. 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 😊

  19. 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

  20. 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

  21. 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

  22. 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

  23. 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

  24. In fact our talk about "Reproducible environments is all you need" during #rsecon24 is on youtube. If you're interested how to make your project more reproducible and easier to participate for others, check it out:

    youtube.com/watch?v=YX90-ZoJ_T

    You can also find the presentation here:

    zenodo.org/records/14290309

    I already did some PRs to other projects including a `devbox.json` - it's really useful to have the "correct" version of all those developer tools.

    #devbox #development

  25. In fact our talk about "Reproducible environments is all you need" during #rsecon24 is on youtube. If you're interested how to make your project more reproducible and easier to participate for others, check it out:

    youtube.com/watch?v=YX90-ZoJ_T

    You can also find the presentation here:

    zenodo.org/records/14290309

    I already did some PRs to other projects including a `devbox.json` - it's really useful to have the "correct" version of all those developer tools.

    #devbox #development

  26. lets see what happend when you're testing #gitlab runner locally by using podman with podman-desktop.io/docs/migrati and #devbox as package installer for the project

  27. lets see what happend when you're testing #gitlab runner locally by using podman with podman-desktop.io/docs/migrati and #devbox as package installer for the project

  28. lets see what happend when you're testing #gitlab runner locally by using podman with podman-desktop.io/docs/migrati and #devbox as package installer for the project

  29. if you're using #devbox tool by #nix dont use "ansible-later" package, instead use "ansible" #devops

  30. if you're using #devbox tool by #nix dont use "ansible-later" package, instead use "ansible" #devops

  31. if you're using #devbox tool by #nix dont use "ansible-later" package, instead use "ansible" #devops