[
https://issues.apache.org/jira/browse/PIO-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15500297#comment-15500297
]
ASF GitHub Bot commented on PIO-26:
---
Github user jj870la commented on the issue:
https:
[
https://issues.apache.org/jira/browse/PIO-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15500291#comment-15500291
]
ASF GitHub Bot commented on PIO-26:
---
Github user jj870la commented on the issue:
https:
[
https://issues.apache.org/jira/browse/PIO-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15500281#comment-15500281
]
ASF GitHub Bot commented on PIO-26:
---
Github user jj870la commented on the issue:
https:
Hello folks,
Great to hear about this possibility. I've been working on running PredictionIO
on Heroku https://www.heroku.com
Heroku's 12-factor architecture https://12factor.net prefers "stateless builds"
to ensure that compiled artifacts result in processes which may be cheaply
restarted, re
Hate to make more work for you but the new name would also maybe avoid some
confusion for older migrating users.
On Sep 16, 2016, at 9:02 AM, Donald Szeto wrote:
If everyone agrees that the artifacts should have an "apache-" prefix, I
will roll an RC2 shortly. Since the namespace change is unav
Yes, a new thing though it might serve some of the same purposes. The idea is
to only use engine instance information from the metadata store so the template
commands will work from anywhere and mostly in any order. On a cluster machine
if the engine instance data is in the metastore and the bin
