Component Updating

Following Mantra Development Paradigm, the updating of a component to a new version should be an easy task.

This is the thumb of the rule: continuous updating of the project results in a smaller migrations with less effort and conflicts.

If the functionality of the component and its entity models are easy and simple as well, then the update process should be trivial, that's one of the reason (only one of them), by which Mantra tries you to develop small and decoupled components with simple data modes.

On the other hand, Mantra expects to update components incrementally, to simplify this task even more.

Mantra detects if a compoment should be updated if its version indicated in mantra.json file has changed and if it is different than the version of the component currently installed.

As an example, if the mantra.json file for the current component changes from:

{
    "name" : "mycomponent",
    "version" : "1.0.0",
}

, to:

{
    "name" : "mycomponent",
    "version" : "1.0.1",
}

Then, this component should be updated. This update can involve model updates or not, depending of the nature of the component.

Mantra will not run the application until the components needed to updated are updated with success.

To update the component, update command is used:

$ mantrad update

By running this command, Mantra will look for components to be updated.

If found, then Mantra will call onUpdate method of the Install property of the component.

Any activity needed for the updating, should be placed in onUpdate method.

Refer to Updating Components Data Models of the documentation to read same examples.

To learn by example, go to Mantra demos and components sections of Mantra site.