> For the complete documentation index, see [llms.txt](https://docs.eximee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eximee.com/documentation/documentation-en/eksploatacja-aplikacji/designer/srodowiska.md). # Environment Module {% hint style="info" %} The availability of functionality depends on the license and may not be available in all deployments. {% endhint %} The module is used to manage application templates. It enables: * viewing the version of the selected application on the available environments, * migrating the application template (together with its dependencies) between environments, * reverting the last application migration on a specific environment (rollback), * launching the selected application on the selected environment in the simulator (see Application Simulator), * downloading the business package (the application template together with the dependencies required to run it on the environment). ## Displaying application information on environments After going to the module, the button is displayed **APPLICATION**.

Figure 1. Tab "Environments"

After selecting an application from the list, the published and highest version of the application will be displayed on each of the available environments:

Figure 2. Application status on individual environments

## Launching the application Clicking the button next to the published version redirects to the application simulator module, automatically selecting the environment from which the redirect occurred. ## Template migration To migrate the application together with dependencies to a higher environment, click the arrow between the tiles:

Figure 3. Arrow migrating the application to a higher environment

This will migrate and publish the template in the highest version to the specified environment. In addition, the files necessary for the application to function correctly will be imported to the appropriate directories on the environment. Template migration is performed only on the first environment, due to the shared database for all LAN instances. The application dependencies, however, are delivered to all instances. ### Validation during template migration Before migrating the template together with dependencies, environment consistency is validated. The validator checks whether the dependencies imposed on the target environment will not introduce inconsistencies. If the validator encounters any problems, it will display a list and the content of warnings to the user. At this point, the user can decide whether they still want to force the migration to the target environment.

Figure 4. Migration error message

## Environment action menu To open the environment action menu, press the button **Open action menu** located in the upper-right corner of the environment tile.

Figure 5. Environment action menu

### Template export Clicking the action menu option **Export package** will build a zip file containing the application template in the latest version on the given environment together with the dependencies needed to run it.

Figure 6. Menu containing the package export command

The file will be saved in the Nexus repository. In response, a popup with a link to the package in Nexus will appear in the browser.

Figure 7. Window with a link to the package

* Template export from the repository is performed from the first environment, due to the shared database for all LAN instances. * The visibility of the export option is controlled by the flag from the environment configuration (`bundleExporter`). ### Environment rollback The option **Rollback** is used to restore the last backup of the application dependencies directories on the given environment. Backups are created when any application with dependencies is migrated to the environment. Each environment has its own backup for each application migrated earlier. * Template rollback is performed only on the first environment, due to the shared database for all LAN instances. * The visibility of this option is controlled by the flag from the environment configuration (`migrationTarget`). If no migration has been finalized before, the option will be grayed out, because there is no package available that could be restored. ## Environment configuration The list of available environment "tiles" must be configured in the file whose path should be provided in the package installation parameters (`EXIMEE_CONSOLE_ENVIRONMENTS_CONFIGURATION_PATH`). The order of the provided environments also determines the migration direction. ```json [ { "name": "Environment1", "lanHosts": [ "lan.adres.test" ], "migrationTarget": false, "bundleExporter": false }, { "name": "Environment2", "lanHosts": [ "lan.test.eximee", "lan2.test.eximee" ], "migrationTarget": true, "bundleExporter": true } ] ``` ### Meaning of the individual attributes: * **`name`** – name of the environment displayed on the tile. * **`lanHosts`** – array of LAN instances on a given environment (it is important that these are only hosts – without, for example, the protocol `http://` or the port). * **`migrationTarget`** – flag indicating whether applications can be migrated to a given environment. * **`bundleExporter`** – flag indicating whether a package with dependencies can be exported from a given environment. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.eximee.com/documentation/documentation-en/eksploatacja-aplikacji/designer/srodowiska.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.