I'm not sure if it's in the scope of this project, but maybe you have some advice on how I should approach this.
We have a web project that has a python backend and javascript frontend which I'm trying to migrate over to nix. The project structure looks approximately like this (note that we have several yarn workspaces defined):
The end goal is to build a resulting package using nix (it should contain both python code and minified js files) as well as to have a development environment where we could start a frontend and backend development servers. So, ideally, running nix build should produce a package and running nix-shell should give a shell where node_modules are available together with all python dependencies.
So my question is if there is, are there any best practices about how to combine two ways to build packages: yarn2nix and something like buildPythonPackage, pip2nix, or setup.nix?
I'm not sure if it's in the scope of this project, but maybe you have some advice on how I should approach this.
We have a web project that has a python backend and javascript frontend which I'm trying to migrate over to nix. The project structure looks approximately like this (note that we have several yarn workspaces defined):
The end goal is to build a resulting package using nix (it should contain both python code and minified js files) as well as to have a development environment where we could start a frontend and backend development servers. So, ideally, running
nix build
should produce a package and runningnix-shell
should give a shell wherenode_modules
are available together with all python dependencies.So my question is if there is, are there any best practices about how to combine two ways to build packages: yarn2nix and something like
buildPythonPackage
, pip2nix, or setup.nix?Will appreciate any input on this.