You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First, the name of the Shutdown script is confusing and misleading. Since it is run when a channel is undeployed (not when MC is shut down), it should be renamed to the "Undeploy" script. In addition to being a better descriptor, it would also indicate that it's essentially the complement to the Deploy script.
Next, in addition to the four global scripts that we now currently have, we should also have true server startup and shutdown scripts. The "Server Startup" script would be the first script called when the server starts up (and therefore before any Deploy scripts). Likewise, the "Server Shutdown" script would be the last script called before the server shuts down.
This would make any necessary cleanup much easier, as one wouldn't have to add code in a shutdown script to make sure that there are no other channels still deployed.
First, the name of the Shutdown script is confusing and misleading. Since it is run when a channel is undeployed (not when MC is shut down), it should be renamed to the "Undeploy" script. In addition to being a better descriptor, it would also indicate that it's essentially the complement to the Deploy script.
Next, in addition to the four global scripts that we now currently have, we should also have true server startup and shutdown scripts. The "Server Startup" script would be the first script called when the server starts up (and therefore before any Deploy scripts). Likewise, the "Server Shutdown" script would be the last script called before the server shuts down.
This would make any necessary cleanup much easier, as one wouldn't have to add code in a shutdown script to make sure that there are no other channels still deployed.
Imported Issue. Original Details:
Jira Issue Key: MIRTH-3312
Reporter: ericb
Created: 2014-06-02T16:28:57.000-0700
The text was updated successfully, but these errors were encountered: