# Edge command line install with specific modules

**URL:** <https://forum.inductiveautomation.com/t/edge-command-line-install-with-specific-modules/115693>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [May 25, 2026, 11:27pm UTC](https://forum.inductiveautomation.com/t/edge-command-line-install-with-specific-modules/115693 "2026-05-25T23:27:37Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![kcollins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kcollins/32/19646_2.png) [@kcollins](https://forum.inductiveautomation.com/u/kcollins)\
**Post date:** [June 3, 2026, 6:33pm UTC](https://forum.inductiveautomation.com/t/edge-command-line-install-with-specific-modules/115693/13 "2026-06-03T18:33:06Z")

</div>

The `GATEWAY_MODULES_ENABLED` environment variable is only meaningful to a starting/running Ignition Gateway (i.e. it is not known to the installer). While typically leveraged in a Docker context, it is actually part of the Ignition platform and will also work in other OS's such as Windows. However, setting up environment variables for Windows services is not very straightforward.

[This forum post](https://forum.inductiveautomation.com/t/gateway-commissioning-eam-upgrade/75328/5) shows the Windows Registry modifications for a given service definition and how to define environment variables.

[This docs page](https://docs.inductiveautomation.com/docs/8.3/platform/docker-image#module-identifiers-table) shows what identifiers can be used in that comma-delimited list. As mentioned there, if you're on Ignition 8.1.x, there are separate "legacy" identifiers that must be used.

---

_[View the full topic](https://forum.inductiveautomation.com/t/edge-command-line-install-with-specific-modules/115693)._