I want to stay up-to-date and have created a new plone project using cookieplone (and uv). Now I want to move code and configuration from my older cookieplone created project to this new project.
In the older project I have a lot source checkouts in my mx.ini.
I have found
but I’m wondering if/how this can replace mx-dev?
How to automate the “git clone”? For CI: Do I have to manually add a script that checkout all the sources before “make install”? Or did I miss something?
We didn’t recommend a way to handle git clone because I don’t think there is consensus on the best way to do that yet in a uv-managed project.
mxdev recently gained the ability to update [tool.uv.sources] in pyproject.toml, so that might help. (Edit pyproject.toml file's `tool.uv.sources` option if it is a uv-managed project by erral · Pull Request #81 · mxstack/mxdev · GitHub) But you would need to modify the Makefile generated by cookieplone-templates in order to make it again run mxdev before the normal uv sync.
The point is that if we have the code in git we do not need editable checkouts what we got when using mxdev.
If you just point to the source in [uv.tool.sources] uv will manage to download the source and build it in your project.
Another story is the need to have editable checkouts of other dependencies while in development, for that you will need something like David explained.