[ https://issues.apache.org/jira/browse/PIO-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chan updated PIO-47: -------------------- Description: As discussed in the dev mailing list, removing engine manifest would be the first step in improving the workflow towards a more modular design. - Remove manifest.json completely. `pio build` will be stateless, and will not write anything to the database. This will make it easier to compile/build on PaaS platforms such as Heroku. Later, we can remove `pio build` command entirely, so that PIO is independent of the build tool (sbt). - An immediate major disadvantage would be not being able to run pio commands outside of the engine directory. This can be resolved in the next step of creating a general metadata registry. - Meanwhile, we can use engineFactory as *engineId* , and SHA-1 hash of engine filepath as *engineVersion* (as before). We can improve this when designing a metadata registry, was: As discussed in the dev mailing list, removing engine manifest would be the first step in improving the workflow towards a more modular design. - Remove manifest.json completely. `pio build` will be stateless, and will not write anything to the database. This will make it easier to compile/build on PaaS platforms such as Heroku. Later, we can remove `pio build` command entirely, so that PIO is independent of the build tool (sbt). - An immediate major disadvantage would be not being able to run pio commands outside of the engine directory. This can be resolved in the next step of creating a general metadata registry. - Meanwhile, we can use engineFactory as **engineId**, and SHA-1 hash of engine filepath as **engineVersion** (as before). We can improve this when designing a metadata registry, > Remove engine manifest for stateless build > ------------------------------------------ > > Key: PIO-47 > URL: https://issues.apache.org/jira/browse/PIO-47 > Project: PredictionIO > Issue Type: New Feature > Reporter: Chan > > As discussed in the dev mailing list, removing engine manifest would be the > first step in improving the workflow towards a more modular design. > - Remove manifest.json completely. `pio build` will be stateless, and will > not write anything to the database. This will make it easier to compile/build > on PaaS platforms such as Heroku. Later, we can remove `pio build` command > entirely, so that PIO is independent of the build tool (sbt). > - An immediate major disadvantage would be not being able to run pio commands > outside of the engine directory. This can be resolved in the next step of > creating a general metadata registry. > - Meanwhile, we can use engineFactory as *engineId* , and SHA-1 hash of > engine filepath as *engineVersion* (as before). We can improve this when > designing a metadata registry, -- This message was sent by Atlassian JIRA (v6.3.4#6332)