# :extra-paths in ions deployment

**URL:** https://forum.datomic.com/t/extra-paths-in-ions-deployment/1193
**Category:** Datomic Cloud
**Created:** [October 4, 2019, 11:10am UTC](https://forum.datomic.com/t/extra-paths-in-ions-deployment/1193 "2019-10-04T11:10:33Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![tslocke](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.datomic.com/tslocke/32/233_2.png) [@tslocke](https://forum.datomic.com/u/tslocke)
#### Post date: [October 4, 2019, 11:10am UTC](https://forum.datomic.com/t/extra-paths-in-ions-deployment/1193/1 "2019-10-04T11:10:34Z")

</div>

My codebase has directories `env/dev` and `env/prod`, under which are defined alternative versions of the same namespace `my-app.env`. The directories are not included in the regular `:paths` in deps.edn, but are added as `:extra-paths` under aliases for `:dev` and `:prod`.

When deploying using ions, `my-app.env` is not found, and the deploy fails.

Is there a way to configure things so that the options under the `:prod` alias are active in the deployed version? For now I’ve just added the prod dir to the top-level `:paths`, and the deploy succeeds.

If there’s a more idiomatic way to achieve the same thing, that would be even better.

Thanks in advance.