Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
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,
Attachments
Issue Links
- links to