-
Notifications
You must be signed in to change notification settings - Fork 66
Deploy modules not honoring modules root #371
Comments
Sure that is a bug? I'd expect src/ paths to load as is.. |
Let's say I have my modules root set in my http server to /app/version2/. That means that my http server treats /app/version2/ as / when service up xquery files. Now if my src/ dir on my drive looks like: src/some.xqy and it gets loaded on the server to /some.xqy then it will be invisible to my appserver. But if we make the change I proposed above, the file will be loaded to /app/version2/some.xqy and will appear to the http server as /some.xqy. @grtjn do you still think it's not a bug? |
I think it depends on what you would expect the deployer to do. :) How I used it:
So, if you have an app with /app/version2/ as root, I'd expect some.xqy on the path src/app/version2/some.xqy I do see where you want to go, but that is new functionality I think. I would propose introducing a new property for that, something like modules-root-prefix=/app/version2 |
Or better: |
Ok, Geert. I agree that it is an enhancement rather than a bug. And I like modules-prefix. I'll add a modules-prefix=/ to the default.properties and then in server_config.rb I'll do: total_count = load_data xquery_dir,
:add_prefix => @properties["ml.modules-prefix"],
:remove_prefix => xquery_dir, Sound good to you? |
Sounds excellent! :) |
@paxtonhare were you working on a PR for this? |
I had planned to work on it but got distracted. No current plans to do this right now. |
Fixed #371: added modules-prefix support
server_config.rb line 1155ish:
should be:
The text was updated successfully, but these errors were encountered: