Github user dszeto commented on the issue:
    @pferrel For `pio build` we probably can enhance it such that it can take a 
working directory for compilation to run. If we look at some other build tools, 
they also rely on having certain files in the current working directory.
    For `pio train` and `pio deploy`, I absolutely agree that it should be able 
to run from anywhere as the most advanced scenario. My personal take to this 
change would be something comparable to a local HBase and distributed HBase 
setup. It would be ideal if someone can start playing with PredictionIO without 
setting up any external services (not even a SQL database). I believe Chan's 
change here is a partial step to make the learning curve less steep, and path 
ways for us to untangle engine registration so that it could become a feature 
that can be more easily documented and understandable.
    Do you currently have any production deployments that rely heavily on 
engine IDs and versions? That would be a bigger immediate concern regarding 
this change.

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

Reply via email to