# Best practices on how to boot dependescies based on env

**URL:** <https://discourse.dry-rb.org/t/best-practices-on-how-to-boot-dependescies-based-on-env/254>\
**Category:** Uncategorized\
**Created:** [April 20, 2017, 12:57pm UTC](https://discourse.dry-rb.org/t/best-practices-on-how-to-boot-dependescies-based-on-env/254 "2017-04-20T12:57:58Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![alexandru-calinoiu](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.dry-rb.org/alexandru-calinoiu/32/98_2.png) [@alexandru-calinoiu](https://discourse.dry-rb.org/u/alexandru-calinoiu)\
**Post date:** [April 20, 2017, 12:57pm UTC](https://discourse.dry-rb.org/t/best-practices-on-how-to-boot-dependescies-based-on-env/254/1 "2017-04-20T12:57:58Z")

</div>

Hi,

I will like to boot ‘real’ dependencies in production env and ‘fake’ ones on development and test env. Did you tried that before? How did it worked out?

---

<div class="post-metadata">

**Author:** ![solnic](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.dry-rb.org/solnic/32/779_2.png) [@solnic](https://discourse.dry-rb.org/u/solnic)\
**Post date:** [April 20, 2017, 1:40pm UTC](https://discourse.dry-rb.org/t/best-practices-on-how-to-boot-dependescies-based-on-env/254/2 "2017-04-20T13:40:49Z")

</div>

Such feature is not supported. Feel free to report a feature request and we could discuss it there. For now you’d have to use a custom component loader that would look at environment and decide which dependency should be loaded.

---

<div class="post-metadata">

**Author:** ![alexandru-calinoiu](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.dry-rb.org/alexandru-calinoiu/32/98_2.png) [@alexandru-calinoiu](https://discourse.dry-rb.org/u/alexandru-calinoiu)\
**Post date:** [April 20, 2017, 3:06pm UTC](https://discourse.dry-rb.org/t/best-practices-on-how-to-boot-dependescies-based-on-env/254/3 "2017-04-20T15:06:41Z")

</div>

Got it, request features happens in github?

I am basically doing a bunch of `case` statements a lot ☹

---

<div class="post-metadata">

**Author:** ![solnic](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.dry-rb.org/solnic/32/779_2.png) [@solnic](https://discourse.dry-rb.org/u/solnic)\
**Post date:** [April 20, 2017, 3:25pm UTC](https://discourse.dry-rb.org/t/best-practices-on-how-to-boot-dependescies-based-on-env/254/4 "2017-04-20T15:25:02Z")

</div>

> [@alexandru-calinoiu](#):
>
> Got it, request features happens in github?

yes please

> [@alexandru-calinoiu](#):
>
> I am basically doing a bunch of case statements a lot

yeah as I said, we have some building blocks to enable this, but it’s not a 1st-class feature yet.