mach-nix-template
devbox
mach-nix-template | devbox | |
---|---|---|
7 | 48 | |
67 | 7,536 | |
- | 4.5% | |
0.0 | 9.7 | |
over 1 year ago | 6 days ago | |
Nix | Go | |
- | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
mach-nix-template
-
Struggling with Python dependencies conflicts and NixOS
Hi! Yes, there is a solution to your problem! I used my popular project mach-nix-template to generate a python-environment.
-
Python Flake and Direnv
This happened, because you only copied the text from the flake.nix file you found here. You did not copy over the flake.lock file, which stores information about what version of nixpkgs and other dependencies your software uses. This led to an incompatibility. I am sorry, I forgot to mention that the flake.lock file needs to be present as well. I updated the readme accordingly.
-
Can't use pip to install packages
Hey, I had the same issues as you. Therefore I created the following nix flake: https://github.com/Quoteme/mach-nix-template
-
Development shell with pros-cli available
I started with this template.
- I created a super simple flake.nix template so you can finally use python painlessly in your nix projects. Just copy a few lines over into your flake.nix and you can use all of PyPi :)
devbox
-
How I use Devbox in my Elm projects
Before I went on my Christmas vacation last year I wrote an article on how I use Nix in my Elm projects. At the time, I was pleased with my set up. However, not even a month would go by before my satisfaction was questioned. In early January, Carlo Ascani asked a question, on the Elm Discourse, about his Umbra project. I decided to explore his project and I soon discovered two files, devbox.json and devbox.lock, I had never seen before. This piqued my curiosity and I had to learn more. I followed the link to the Devbox website and feverishly read the docs. I... was... hooked. I was pleasantly surprised by its simplicity and it seemed to fit my use cases really well.
-
Show HN: Flox 1.0 – Open-source dev env as code with Nix
How does Flox compare to Devbox? https://github.com/jetpack-io/devbox
- Instant, easy, and predictable development environments on any machine
-
PackagingCon – a conference only for software package management
I've spent the last year managing all my packages with Devbox (https://github.com/jetpack-io/devbox).
Local dev, cloud dev, CI, production – all with the same config file. Fingers crossed my talk submission for PackagingCon gets accepted. It'd be awesome to share this new way of working with a wider audience.
-
NixOS and My Descent into Insanity
> Now to figure out what a "flake" is…
Flake is a worthwhile addition to Nix that is worth learning. But like anything Nixian, it's not straightforward.
Have you checked out any of the tools that aim to simplify Nix experience? We built Devbox (https://github.com/jetpack-io/devbox) with this in mind.
-
TySON: a native go library that lets you use TypeScript as an embedded configuration language without depending on Node or V8
Also devbox ( https://github.com/jetpack-io/devbox ) which is what this is for does not work on windows because of its Nix dependency.
-
Simplifying preview environments for everyone
For these reasons, I believe most developer environments should prioritize developer experience over fidelity. Tools like Containerized development environments and cloud emulators can strike the right balance and there’s no surprise that we see increased activity around devcontainers, and similar solutions.
-
Codespaces but open-source, client-only, and unopinionated
Local first, cloud optional is the only way (IMHO) we're going to get people off their local laptop development setups.
We need to support local dev environments first, with the exact same config a developer can then move to the cloud.
See https://github.com/jetpack-io/devbox for how this can be achieved and https://www.mikenikles.com/blog/dev-environments-in-the-clou... for my thoughts after 3 years of working in this space.
-
Why did Nix adopt Flakes?
If you like the properties of Nix, but find it confusing, you should check out Devbox! It simplifies the process of creating Nix-powered dev environments:
https://github.com/jetpack-io/devbox
-
NixTest: a tiny unit testing framework written in pure nix
As part of the work we've been doing with [devbox](https://github.com/jetpack-io/devbox), we needed a unit testing framework to test some of our nix code. Unfortunately we had some use cases where we did *not* want to introduce a dependency on `nixpkgs` (and therefore we couldn't use `runTests`).