The mix supports a feature for archiving projects. It might be useful for releasing the engine and shipping it to the community. Besides the engine, releases should include the sirko js library.
For example, an instance of the app is hosted on http://sirko.example.org. To require the sirko js library, the client references it like http://sirko.example.org/sirko.js.
It will simplify the installation for clients who don't use Npm or don't want to add a new dependency to their package.json.
Also, there is a distillery library which looks promising to manage releases. We need to evaluate both options and choose the best one.
The mix supports a feature for archiving projects. It might be useful for releasing the engine and shipping it to the community. Besides the engine, releases should include the sirko js library.
For example, an instance of the app is hosted on
http://sirko.example.org
. To require the sirko js library, the client references it likehttp://sirko.example.org/sirko.js
.It will simplify the installation for clients who don't use Npm or don't want to add a new dependency to their package.json.
Also, there is a distillery library which looks promising to manage releases. We need to evaluate both options and choose the best one.