Search: "deploy architecture"

The unexpected maintenance resulted in a user pressing the Apply to Environment button in Deploy -> Architecture in eMagiz. As a result, the complete machine was stopped, recreated, and started again. == 2.

The reset runtime action in the Deploy Architecture cleans up the data folder (excluding the H2 folder) but doesn't cleanup the libraries.

Situation == Pressing the 'Apply to Environment' button in Deploy Architecture led to an 'Update rollback complete' state. == 2. Problem == The problem in this case was that two routes were pointing at the same port configured in Deploy Architecture. == 3. Analysis == === 3.1 Reproduction === N/A === 3.2 Analysis === We started off by checking the CloudFormation in AWS.

This can be done by moving to Deploy -> Architecture and pressing 'Reset H2'. Do remember that resetting the H2 database or removing and readding it will result in a loss of all the data on the database. == 5.

. * The first is to execute a "restart runtime" action via Deploy Architecture or the on-premise server. * Secondly, you could deploy a new version of the infra (via the Releases functionality).

. ** For example, when you command the container to stop via Deploy Architecture or when eMagiz stops the container, e.g.