Repository navigation
Support remote mx.ini and requirements-in.txt ? #97
Description
At Plone currently if you change plone.base and need those changes (still not released) in plone.batching you are out of look (within plone.batching repository). You can only test the combination in Jenkins, or ask for a release of plone.base and, only after that, you can actually test it in plone.batching.
Adding buildout.cfg was the solution back then, but we want to steer away from it, so mxdev is the right answer (?)
Now though, adding mx.ini and requirements-in.txt on every single repository and maintaining those is not practical at all. We would have to create ~100 PRs for each repository that has unreleased changes merged and ~100 PRs more whenever it is released...
Is there a way to point mxdev to a remote mx.ini ? i.e. https://github.com/plone/buildout.coredev/blob/6.2/mx.ini (that should then also fetch remotely the requirements-in ?
What would be perfect for our use case would be to be able to call directly mxdev -c REMOTE-mx.ini so that no file has to be stored on the repository, only the reference to the remote mx.ini on tox.ini.
Activity
gforcada commentedon Jul 13, 2026
Oh, sorry, I should have played more with
mxdevbefore reporting the issue.So
mxdev -c REMOTE-URLdoes work, but what does not work is that if the remote URL has includes, somehow part of the parent URL is missing.When calling;
mxdev -c https://raw.githubusercontent.com/plone/buildout.coredev/refs/heads/6.2/mx.iniThe first download works, but the includes get
http_parentas'https://raw.githubusercontent.com/plone/buildout.coredev/refs/heads/6.2'and when doingparse.urljoin(http_parent, file_or_url)the6.2somehow gets lost. A trailing/is missing.