# Extension dev: accessing the current config

**URL:** <https://discourse.mopidy.com/t/extension-dev-accessing-the-current-config/4782>\
**Category:** Help and support\
**Created:** [February 25, 2021, 10:12am UTC](https://discourse.mopidy.com/t/extension-dev-accessing-the-current-config/4782 "2021-02-25T10:12:11Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![BlueLineSwinger](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/bluelineswinger/32/1974_2.png) [@BlueLineSwinger](https://discourse.mopidy.com/u/BlueLineSwinger)\
**Post date:** [February 25, 2021, 10:12am UTC](https://discourse.mopidy.com/t/extension-dev-accessing-the-current-config/4782/1 "2021-02-25T10:12:11Z")

</div>

I’m presently working on a possible backend extension for Mopidy. The structure of the extension necessitates the creation of classes that require some info from the current config. However, they cannot have the config object simply passed in as they are not instantiated in the normal way.

I can work around this, but I’d like to know if there is some other proper way to get the current config, such as some Mopidy function that can be imported into the module. I’m not finding anything in the docs that fits, but certainly could be missing something.

Thanks.

---

<div class="post-metadata">

**Author:** ![system](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/system/32/1_2.png) [@system](https://discourse.mopidy.com/u/system)\
**Post date:** [August 26, 2021, 10:12pm UTC](https://discourse.mopidy.com/t/extension-dev-accessing-the-current-config/4782/2 "2021-08-26T22:12:55Z")

</div>

Closed on August 26, 2021, 10:12pm UTC

This topic was automatically closed 182 days after the last reply. New replies are no longer allowed.
