File contents Post-Env Setting
Manage and configure post-orch.env settings.
What this does
Reviews current post-orch.env configuration
Updates deployment profile
Configures IP addresses for services
Sets feature flags
Validates configuration for deployment
Usage
Use this skill when you want to:
Review post-orch configuration
Change deployment profile
Configure service IP addresses
Enable/disable features
Set component versions
Manage post-orch.env by:
Show current configuration :cat post-orch/post-orch.env
Key settings to review :
DEPLOYMENT_PROFILE : onprem-eim or onprem-vproEOM_ORCH_IP : Orchestrator service IPEOM_TRAEFIK_IP : Traefik ingress IPEOM_HAPROXY_IP : HAProxy IP (if separate)VERSION_TAGS : Component version overridesENABLE_ *: Feature flags for componentsProxy settings :
EOM_HTTP_PROXY : HTTP proxy URL for orchestrator servicesEOM_HTTPS_PROXY : HTTPS proxy URL for orchestrator servicesEOM_NO_PROXY : Comma-separated list of hosts/CIDRs to bypass proxy
Edge Node Proxy settings :
EOM_EN_HTTP_PROXY : HTTP proxy for edge nodesEOM_EN_HTTPS_PROXY : HTTPS proxy for edge nodesEOM_EN_FTP_PROXY : FTP proxy for edge nodesEOM_EN_SOCKS_PROXY : SOCKS proxy for edge nodesEOM_EN_NO_PROXY : No-proxy list for edge nodes
Update settings as requested:
Edit specific lines
Validate values
Check consistency with profile
Profile-specific considerations :
onprem-eim : Standard deployment with EIMonprem-vpro : Includes Intel vPro management
Special configurations :
Coder/single-IP : All service IPs same as Coder hostMulti-IP : Separate IPs for Traefik, HAProxy, OrchestratorDevelopment : Use default settings
Validate configuration :
IP addresses valid and from MetalLB range
Profile matches environment files
Feature flags consistent
Required variables set
No conflicting settings
Report configuration summary and any issues found
Common settings :
# Standard on-prem EIM
DEPLOYMENT_PROFILE=onprem-eim
EOM_ORCH_IP=192.168.1.240
EOM_TRAEFIK_IP=192.168.1.241
EOM_HAPROXY_IP=192.168.1.242
# vPro deployment
DEPLOYMENT_PROFILE=onprem-vpro
# ... same IPs plus vPro components enabled
# Single-IP Coder
DEPLOYMENT_PROFILE=onprem-eim
EOM_ORCH_IP=10.0.0.100
EOM_TRAEFIK_IP=10.0.0.100
EOM_HAPROXY_IP=10.0.0.100
# Behind corporate proxy
EOM_HTTP_PROXY="http://proxy.corp.com:8080"
EOM_HTTPS_PROXY="http://proxy.corp.com:8080"
EOM_NO_PROXY="localhost,127.0.0.1,10.0.0.0/8,.corp.com"
EOM_EN_HTTP_PROXY="http://proxy.corp.com:8080"
EOM_EN_HTTPS_PROXY="http://proxy.corp.com:8080"
EOM_EN_NO_PROXY="localhost,127.0.0.1,10.0.0.0/8,.corp.com"
Important environment files affected :
post-orch/environments/onprem-eim-settings.yaml.gotmplpost-orch/environments/onprem-eim-features.yaml.gotmplpost-orch/environments/profile-vpro.yaml.gotmpl
1 --- 2 name: post-env-setting 3 description: Manage and configure post-orch.env settings 4 --- 5 6 # Post-Env Setting 7 8 Manage and configure post-orch.env settings. 9 10 ## What this does 11 - Reviews current post-orch.env configuration 12 - Updates deployment profile 13 - Configures IP addresses for services 14 - Sets feature flags 15 - Validates configuration for deployment 16 17 ## Usage 18 Use this skill when you want to: 19 - Review post-orch configuration 20 - Change deployment profile 21 - Configure service IP addresses 22 - Enable/disable features 23 - Set component versions 24 25 --- 26 27 Manage post-orch.env by: 28 1. **Show current configuration**: 29 ```bash 30 cat post-orch/post-orch.env 31 ``` 32 2. **Key settings to review**: 33 - **DEPLOYMENT_PROFILE**: `onprem-eim` or `onprem-vpro` 34 - **EOM_ORCH_IP**: Orchestrator service IP 35 - **EOM_TRAEFIK_IP**: Traefik ingress IP 36 - **EOM_HAPROXY_IP**: HAProxy IP (if separate) 37 - **VERSION_TAGS**: Component version overrides 38 - **ENABLE_***: Feature flags for components 39 - **Proxy settings**: 40 - **EOM_HTTP_PROXY**: HTTP proxy URL for orchestrator services 41 - **EOM_HTTPS_PROXY**: HTTPS proxy URL for orchestrator services 42 - **EOM_NO_PROXY**: Comma-separated list of hosts/CIDRs to bypass proxy 43 - **Edge Node Proxy settings**: 44 - **EOM_EN_HTTP_PROXY**: HTTP proxy for edge nodes 45 - **EOM_EN_HTTPS_PROXY**: HTTPS proxy for edge nodes 46 - **EOM_EN_FTP_PROXY**: FTP proxy for edge nodes 47 - **EOM_EN_SOCKS_PROXY**: SOCKS proxy for edge nodes 48 - **EOM_EN_NO_PROXY**: No-proxy list for edge nodes 49 3. **Update settings** as requested: 50 - Edit specific lines 51 - Validate values 52 - Check consistency with profile 53 4. **Profile-specific considerations**: 54 - **onprem-eim**: Standard deployment with EIM 55 - **onprem-vpro**: Includes Intel vPro management 56 5. **Special configurations**: 57 - **Coder/single-IP**: All service IPs same as Coder host 58 - **Multi-IP**: Separate IPs for Traefik, HAProxy, Orchestrator 59 - **Development**: Use default settings 60 6. **Validate configuration**: 61 - IP addresses valid and from MetalLB range 62 - Profile matches environment files 63 - Feature flags consistent 64 - Required variables set 65 - No conflicting settings 66 7. **Report configuration summary** and any issues found 67 68 **Common settings**: 69 ```bash 70 # Standard on-prem EIM 71 DEPLOYMENT_PROFILE=onprem-eim 72 EOM_ORCH_IP=192.168.1.240 73 EOM_TRAEFIK_IP=192.168.1.241 74 EOM_HAPROXY_IP=192.168.1.242 75 76 # vPro deployment 77 DEPLOYMENT_PROFILE=onprem-vpro 78 # ... same IPs plus vPro components enabled 79 80 # Single-IP Coder 81 DEPLOYMENT_PROFILE=onprem-eim 82 EOM_ORCH_IP=10.0.0.100 83 EOM_TRAEFIK_IP=10.0.0.100 84 EOM_HAPROXY_IP=10.0.0.100 85 86 # Behind corporate proxy 87 EOM_HTTP_PROXY="http://proxy.corp.com:8080" 88 EOM_HTTPS_PROXY="http://proxy.corp.com:8080" 89 EOM_NO_PROXY="localhost,127.0.0.1,10.0.0.0/8,.corp.com" 90 EOM_EN_HTTP_PROXY="http://proxy.corp.com:8080" 91 EOM_EN_HTTPS_PROXY="http://proxy.corp.com:8080" 92 EOM_EN_NO_PROXY="localhost,127.0.0.1,10.0.0.0/8,.corp.com" 93 ``` 94 95 **Important environment files affected**: 96 - `post-orch/environments/onprem-eim-settings.yaml.gotmpl` 97 - `post-orch/environments/onprem-eim-features.yaml.gotmpl` 98 - `post-orch/environments/profile-vpro.yaml.gotmpl`
commit ff59a6099d
Frequently asked questions How do I install the Post Env Setting skill? Run npx skillmds@latest add open-edge-platform/post-env-setting in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
What does the Post Env Setting skill do? Manage and configure post-orch.env settings It is listed under Coding & Dev Tools on SkillMD.
Is Post Env Setting safe to use? This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
Which AI agents work with Post Env Setting? This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Is Post Env Setting free to use? Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
Who published Post Env Setting? open-edge-platform (@open-edge-platform) published this skill. Their other Agent Skills are listed on their SkillMD profile.
open-edge-platform