We present opam-nix, show how it helps to easily develop, build and test your OCaml projects with Nix
Convert poetry projects to nix automagically [maintainer=] - nix-community/poetry2nix
We present opam-nix, show how it helps to easily develop, build and test your OCaml projects with Nix
Nix's Import From Derivation (IFD) can speed up development but also cause slow builds. Learn how IFD works, its pros/cons, and when to use it effectively.
I’ve been operating Sillypaste (source code) - a simple Django pastebin created for dogfooding. In this post I hope to capture some of the painpoints of working with Django, Python, Heroku, and the migration to fly.io. Ever since Heroku sold its soul to SalesForce its been on the decline. Customer service is worse than ever, giving wonderful canned responses to most questions. It used to be free to host Sillypaste on heroku, now is a $17/mo ordeal.
Nix is a broad product with a steep learning curve. It’s capable of everything from installing a single package to managing every file and application on your OS. One useful thing you can do with Nix, even as a complete beginner, is manage your dev environments. Nix lets me have multiple projects on the same system that each have their own independent view of what dependencies are available. I can have one legacy project running Python 2.7 and Node.js 4.x alongside a modern project running Python 3.11 and Node.js 20, and they won’t interfere with each other.
For several years now I’ve been using Dokku on my personal webserver as an easy way to spin up new web apps I want to play aroundwith. Like the Heroku platfo...
Automating documentation deployment with Travis, rake and nix Background In the previous post we generated documentation using Doxygen with Exhale to handle Sphinx. Now we will clean up the earlier workflow with rake and ensure the environment is reproducible with nix while deploying to Travis CI. Setup A quick reminder of the setup we generated in the last post: 1tree -d $prj/ -L 2 . ├── docs │ ├── Doxygen │ └── Sphinx ├── nix │ └── pkgs ├── projects │ └── symengine └── scripts 8 directories We had further setup files to enable documentation generation with a manual two stage process (handling doxygen and sphinx separately).
Learn how to use Nix to create highly reproducible Python builds that are aware of native dependencies.