https://docs.mappingsuite.com/w/index.php?action=history&feed=atom&title=Translations%3AOPALE%3AdeploiementEnvironnement_MAPDEPLOY%2F3%2FenTranslations:OPALE:deploiementEnvironnement MAPDEPLOY/3/en - Historique des versions2026-04-08T05:54:25ZHistorique des versions pour cette page sur le wikiMediaWiki 1.32.1https://docs.mappingsuite.com/w/index.php?title=Translations:OPALE:deploiementEnvironnement_MAPDEPLOY/3/en&diff=35864&oldid=prevJdieu : Page créée avec « ==Principle of operation== The MAPDPELOY command (accessible via the Exploitation / Environment Deployment meny) allows you to deploy a staging environment to a production... »2024-11-05T10:16:17Z<p>Page créée avec « ==Principle of operation== The MAPDPELOY command (accessible via the Exploitation / Environment Deployment meny) allows you to deploy a staging environment to a production... »</p>
<p><b>Nouvelle page</b></p><div>==Principle of operation==<br />
The MAPDPELOY command (accessible via the Exploitation / Environment Deployment meny) allows you to deploy a staging environment to a production environment. <br />
Indeed, in good practice, it is advisable not to generate the models or to create the rules/actions directly on the production environment but on the pre-production environment. Once the processing(s) have been validated on this pre-production environment, it is necessary to send its configuration to the production environment. (Model, rules, actions, etc.).<br />
To do this, it is very convenient to use the environment deployment menu. This allows you to fill in the recipient hosts, select the format(s) to send or delete or to send the entire configuration (all formats, rules and actions)</div>Jdieu