# Q: How to create an Execution Environment in a Dev environment with non-Galaxy collections and roles under development?

**URL:** <https://forum.ansible.com/t/q-how-to-create-an-execution-environment-in-a-dev-environment-with-non-galaxy-collections-and-roles-under-development/7859>\
**Category:** Get Help\
**Tags:** galaxy-ng, ee\
**Created:** [August 15, 2024, 2:03am UTC](https://forum.ansible.com/t/q-how-to-create-an-execution-environment-in-a-dev-environment-with-non-galaxy-collections-and-roles-under-development/7859 "2024-08-15T02:03:36Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![snesbitt](https://avatars.discourse-cdn.com/v4/letter/s/8edcca/32.png) [@snesbitt](https://forum.ansible.com/u/snesbitt)\
**Post date:** [August 15, 2024, 2:03am UTC](https://forum.ansible.com/t/q-how-to-create-an-execution-environment-in-a-dev-environment-with-non-galaxy-collections-and-roles-under-development/7859/1 "2024-08-15T02:03:36Z")

</div>

Bottom line, how do I create an execution environment which supports a dev environment?

As part of my Ansible work I have been developing a number of organization specific collections and roles that are under heavy development and are not - and never will be - available on Ansible Galaxy. It is not at all clear how I can use an EE in a dev environment. There are at least two issues:

1. I can’t figure out how to provide the execution environment with an ansible.cfg that specifies the collections path (or anything else for that matter).
2. I can’t figure out how to provide collections which aren’t in Ansible Galaxy. I’m guessing I could copy them in to the image, but that requires a properly configured ansible.cfg. See #1
3. I really would prefer to mount - at least in a dev environment - my organization specific collections directory and _not_ copy them into container. Having to rebuild the environment for every dev related change is pretty obnoxious.

Any help would be much appreciated.