# Best practice for bootstrap the channel information

**URL:** <https://community.bloomreach.com/t/best-practice-for-bootstrap-the-channel-information/986>\
**Category:** Experience Manager (PaaS/OnPrem)\
**Created:** [April 18, 2019, 9:15am UTC](https://community.bloomreach.com/t/best-practice-for-bootstrap-the-channel-information/986 "2019-04-18T09:15:40Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![ThoLe](https://yyz1.discourse-cdn.com/flex027/user_avatar/community.bloomreach.com/thole/32/98_2.png) [@ThoLe](https://community.bloomreach.com/u/ThoLe)\
**Post date:** [April 18, 2019, 9:15am UTC](https://community.bloomreach.com/t/best-practice-for-bootstrap-the-channel-information/986/1 "2019-04-18T09:15:41Z")

</div>

hi guys,

From Hippo 12 started categorized bootstrap data into 2 part application and development.

> **[Repository Data Modules Structure - BloomReach Experience - Open Source CMS](https://documentation.bloomreach.com/library/concepts/configuration-management/repository-data-modules-structure.html)**
>
> Open Source Enterprise Content Management

  
Let say I have channel name channel-a , so practically we should put the data for the node /hst:hst/hst:configurations/channel-a into development part because basically development environment and production environment will never have same channel configuration.

---

<div class="post-metadata">

**Author:** ![jasper.floor](https://yyz1.discourse-cdn.com/flex027/user_avatar/community.bloomreach.com/jasper.floor/32/28_2.png) [@jasper.floor](https://community.bloomreach.com/u/jasper.floor)\
**Post date:** [April 24, 2019, 9:19am UTC](https://community.bloomreach.com/t/best-practice-for-bootstrap-the-channel-information/986/2 "2019-04-24T09:19:24Z")

</div>

It is not uncommon for development and production to have the same channel configuration. Especially for configuration outside the workspace. If this does not match your use case then you can change the configuration of autoexport (or disable it). This means changes in your sitemap on production will have to be managed manually, which is probably not what you want.

> **[Automatic Export Add-on - BloomReach Experience - Open Source CMS](https://documentation.bloomreach.com/12/library/development/automatic-export-add-on.html)**
>
> Open Source Enterprise Content Management

---

<div class="post-metadata">

**Author:** ![ThoLe](https://yyz1.discourse-cdn.com/flex027/user_avatar/community.bloomreach.com/thole/32/98_2.png) [@ThoLe](https://community.bloomreach.com/u/ThoLe)\
**Post date:** [April 24, 2019, 9:33am UTC](https://community.bloomreach.com/t/best-practice-for-bootstrap-the-channel-information/986/3 "2019-04-24T09:33:11Z")

</div>

Yes you are right @jasper.floor  
But ideally the hst:workspace should be put into development configuration data right ?

---

<div class="post-metadata">

**Author:** ![jasper.floor](https://yyz1.discourse-cdn.com/flex027/user_avatar/community.bloomreach.com/jasper.floor/32/28_2.png) [@jasper.floor](https://community.bloomreach.com/u/jasper.floor)\
**Post date:** [April 24, 2019, 9:52am UTC](https://community.bloomreach.com/t/best-practice-for-bootstrap-the-channel-information/986/4 "2019-04-24T09:52:42Z")

</div>

You would think so, but by default these are not development. This is more of a grey area. It would seem obvious that changes in the channel manager should be environment specific, but even here there can be need to bootstrap data. However, this is marked as content so data is only loaded once and then managed on the environment. But certainly some data should be in development rather than application, for which you can either change auto-export or move the files in your project manually.