-
-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automatic use of local version when requires: ..
is used
#170
Comments
One way to achieve this is to allow some requires:
- https://github.com/django-mobans/docker-mobans
- docker-mobans-pkg
configuration:
template_dir:
- ../docker-mobans/templates
- docker-mobans:/templates
- docker-mobans-pkg:/templates requires:
docker-mobans:
- ../docker-mobans
- https://github.com/django-mobans/docker-mobans
- docker-mobans-pkg The former is more powerful, and keeps the fallback resolution to be only occurring within And the solution could be as simple as allowing any template_dir beginning with However, if using |
Please try the following configuration as you have proposed. With version 0.6.0, it should work automatically, given that ../docker-mobans/templates exists. Jinja2-FSLoader(MultiFS) should stop at ../docer-mobans/templates/ if the file is found.
|
With a mobanfile containing
If I want to test an un-merged change to
docker-mobans
, I need to edit the mobanfile to look for a local versionIt would be nice to have a way to do that change without editing the mobanfile.
The way that would be most suitable for the way we have been setting up repos recently is to convert
however iirc pyexcel often has the local version as submodules so that would mean
This use of a local version could be triggered with a cli flag like
--local-requires
Ideally any modified target includes a header comment describing the different source which was used, but moban doesnt know how to do comments in every language, so that needs to be a separate enhancement, and there are a few quite-old issues which relate to this.
The text was updated successfully, but these errors were encountered: