# Where do i put settings for frameworks in the config?

**URL:** <https://community.shotgridsoftware.com/t/where-do-i-put-settings-for-frameworks-in-the-config/7456>\
**Category:** Pipeline Integrations\
**Tags:** toolkit, configuration\
**Created:** [February 26, 2020, 9:12pm UTC](https://community.shotgridsoftware.com/t/where-do-i-put-settings-for-frameworks-in-the-config/7456 "2020-02-26T21:12:21Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![kramester](https://sea1.discourse-cdn.com/shotgunsoftware/user_avatar/community.shotgridsoftware.com/kramester/32/271_2.png) [@kramester](https://community.shotgridsoftware.com/u/kramester)\
**Post date:** [February 26, 2020, 9:12pm UTC](https://community.shotgridsoftware.com/t/where-do-i-put-settings-for-frameworks-in-the-config/7456/1 "2020-02-26T21:12:21Z")

</div>

Ive got a custom framework that has some configuration settings in the info.yml. I cant figure out where to place the settings in my config so that the framework is able to pick them up. I’ve got a tk-framework-custom.yml in the settings folder in the config. Can someone offer some guidance? I cant find any examples of frameworks with settings.

---

<div class="post-metadata">

**Author:** ![tannaz](https://sea1.discourse-cdn.com/shotgunsoftware/user_avatar/community.shotgridsoftware.com/tannaz/32/32_2.png) [@tannaz](https://community.shotgridsoftware.com/u/tannaz)\
**Post date:** [February 26, 2020, 9:16pm UTC](https://community.shotgridsoftware.com/t/where-do-i-put-settings-for-frameworks-in-the-config/7456/2 "2020-02-26T21:16:40Z")

</div>

Hi Anthony! Any reason you couldn’t put the settings in [`config/env/includes/frameworks.yml`](https://github.com/shotgunsoftware/tk-config-default2/blob/master/env/includes/frameworks.yml)?

[[More on that file in the Default Config’s README](https://github.com/shotgunsoftware/tk-config-default2/blob/master/env/README.md#frameworks)]

---

<div class="post-metadata">

**Author:** ![kramester](https://sea1.discourse-cdn.com/shotgunsoftware/user_avatar/community.shotgridsoftware.com/kramester/32/271_2.png) [@kramester](https://community.shotgridsoftware.com/u/kramester)\
**Post date:** [February 26, 2020, 10:03pm UTC](https://community.shotgridsoftware.com/t/where-do-i-put-settings-for-frameworks-in-the-config/7456/3 "2020-02-26T22:03:08Z")

</div>

That didn’t seem to work. Ive tried quite a few different ways of adding these to the config now. Heres the error in the current iteration:

```
[ERROR tk-nuke] App R:\work\anthony.kramer\github\tk-multi-render failed to initialize. It will not be loaded: Framework configuration Error for tk-framework-deadline_v1.0.x: Could not determine value for key 'web_service_machine' in settings! No specified value and no default value.

```

Here is the code in frameworks.yml

```
frameworks:
  tk-framework-deadline_v1.0.x:
    location:
      name: tk-framework-deadline
      type: dev
      path: R:\work\anthony.kramer\github\tk-framework-deadline

settings.tk-framework-deadline_v1.0.x:
  web_service_machine: test
  web_service_port: 8082
```

---

<div class="post-metadata">

**Author:** ![tannaz](https://sea1.discourse-cdn.com/shotgunsoftware/user_avatar/community.shotgridsoftware.com/tannaz/32/32_2.png) [@tannaz](https://community.shotgridsoftware.com/u/tannaz)\
**Post date:** [February 26, 2020, 10:14pm UTC](https://community.shotgridsoftware.com/t/where-do-i-put-settings-for-frameworks-in-the-config/7456/4 "2020-02-26T22:14:49Z")

</div>

Are you including the `settings.tk-framework-deadline_v1.0.x` block anywhere? In order for that block of YAML to actually be at play in your config, you’ll need to include it in some file ([more on includes here](https://developer.shotgunsoftware.com/487a9f2c/?title=Environment+Configuration+Reference#includes)).

The way that file is structured by default, everything falls under a single `frameworks` block, and that block is included, as a whole into each of the environment config files (ie, config/env/\*.yml) with the following lines:

```auto
includes:
- ./includes/frameworks.yml

```

and

`frameworks: "@frameworks"`

The first block specifies the _file_ from which to include, the second references that `frameworks` block by prepending an `@` to its name: `@frameworks`.

So, I’d suggest just adding your settings to that block in `frameworks.yml`, so your additions would look like:

```auto
frameworks:
  tk-framework-deadline_v1.0.x:
    location:
      name: tk-framework-deadline
      type: dev
      path: R:\work\anthony.kramer\github\tk-framework-deadline
    web_service_machine: test
    web_service_port: 8082

```

Let us know if it’s still not working!

---

<div class="post-metadata">

**Author:** ![kramester](https://sea1.discourse-cdn.com/shotgunsoftware/user_avatar/community.shotgridsoftware.com/kramester/32/271_2.png) [@kramester](https://community.shotgridsoftware.com/u/kramester)\
**Post date:** [February 26, 2020, 11:26pm UTC](https://community.shotgridsoftware.com/t/where-do-i-put-settings-for-frameworks-in-the-config/7456/5 "2020-02-26T23:26:06Z")

</div>

That did it. I was convinced that the word “settings” needed to be in there somewhere like it is for engines and apps. Might be good to add that somewhere in the docs.

---

<div class="post-metadata">

**Author:** ![tannaz](https://sea1.discourse-cdn.com/shotgunsoftware/user_avatar/community.shotgridsoftware.com/tannaz/32/32_2.png) [@tannaz](https://community.shotgridsoftware.com/u/tannaz)\
**Post date:** [February 26, 2020, 11:34pm UTC](https://community.shotgridsoftware.com/t/where-do-i-put-settings-for-frameworks-in-the-config/7456/6 "2020-02-26T23:34:54Z")

</div>

It’s a little esoteric, but it comes down to understanding what is part of the structure of our pipeline configurations in general, and what are conventions that we use in our own configs. `settings` isn’t a keyword; it’s just a word we’ve chosen to use as a convention. The document I linked above, the [Environment Configuration Reference](https://developer.shotgunsoftware.com/487a9f2c/?title=Environment+Configuration+Reference), covers all these details. It’s admittedly a dry read, but hopefully an informative one! 😊

And if you find things in there that are still unclear, I’d love to hear that feedback. Thanks!
