Programming

17488 readers

123 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 1 year ago

MODERATORS

snowe

Ategon

[email protected]

Ditching Docker for Local Development (lgug2z.com)

submitted 1 year ago by [email protected] to c/programming

66 comments fedilink hide all child comments

Some folks on the internet were interested in how I had managed to ditch Docker for local development. This is a slightly overdue write up on how I typically do things now with Nix, Overmind and Just.

you are viewing a single comment's thread
view the rest of the comments

[–] uthredii 4 points 1 year ago* (last edited 1 year ago) (1 children)

That seems like an argument for maintaining a frozen repo of packages, not against containers.

I am not arguing against containers, I am arguing that nix is more reproducible. Containers can be used with nix and are useful in other ways.

an argument for maintaining a frozen repo of packages

This is essentially what nix does. In addition it verifies that the packages are identical to the packages specified in your flake.nix file.

You can only have a truly fully-reproducible build environment if you setup your toolchain to keep copies of every piece of external software so that you can do hermetic builds.

This is essentially what Nix does, except Nix verifies the external software is the same with checksums. It also does hermetic builds.

[–] [email protected] 4 points 1 year ago (2 children)

Nix is indeed cool. I just see it as less practical than maintaining a toolchain for devs to use. Seems like reinventing the wheel, instead of airing-up the tires. I could well be absolutely wrong there - my experience is mainly enterprise software and not every process or tool there is used because it is the best one.

[–] uthredii 2 points 1 year ago (1 children)

I just see it as less practical than maintaining a toolchain for devs to use.

There are definately some things preventing Nix adoption. What are the reasons you see it as less practical than the alternatives?

What are alternative ways of maintaining a toolchain that achieves the same thing?

[–] [email protected] 2 points 1 year ago

I see it as less practical mainly due to the extant tooling and age/maturity of the project.

The ways that I'm most familiar with are use of software like Artifactory - basically a multi-repo. Using such a tool, any package or artifact can be readily retained for future use. Then, for builds, one only needs to ensure that it is used as the package source, regardless of type (PyPy, Docker image, binary, RPM, etc).

Alternatively, one can use individual repos for any relevant package type but that's a bit more overhead to manage.

[–] [email protected] 2 points 1 year ago (1 children)

@nickwitha_k @uthredii I’d like to think a better analogy would be that nix is like using a 3D model of a wheel instead of a compass and a straightedge to make wheels hehe 🙃

[–] [email protected] 1 points 1 year ago

I quite like the sound of Nix, every time I touch on it but haven't really dug in yet. You're making me really want to though.