# Docker compose - load configuration

**URL:** <https://discuss.konghq.com/t/docker-compose-load-configuration/2849>\
**Category:** General\
**Tags:** kong-gateway\
**Created:** [February 19, 2019, 9:46pm UTC](https://discuss.konghq.com/t/docker-compose-load-configuration/2849 "2019-02-19T21:46:33Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![eshepelyuk](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/eshepelyuk/32/164_2.png) [@eshepelyuk](https://discuss.konghq.com/u/eshepelyuk)\
**Post date:** [February 22, 2019, 7:47am UTC](https://discuss.konghq.com/t/docker-compose-load-configuration/2849/4 "2019-02-22T07:47:18Z")

</div>

> [@RFC: Kong native Declarative Config format](https://discuss.konghq.com/t/rfc-kong-native-declarative-config-format/2719):
>
> Hi everyone, We are in the process of designing a native declarative configuration format to be used in Kong. Declarative config — specifying your full configuration in a declarative way, rather than an imperative sequence of Admin API operations — has been a desire from the community for [a](https://github.com/Kong/kong/issues/1465) [while](https://github.com/Kong/kong/issues/528). A number of features that we want to eventually have depend on having a way to specify a full Kong configuration: defining the declarative config format is the foundational step to get there. Declar…

---

_[View the full topic](https://discuss.konghq.com/t/docker-compose-load-configuration/2849)._
