# 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:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![lucazamm](https://avatars.discourse-cdn.com/v4/letter/l/9fc29f/32.png) [@lucazamm](https://discuss.konghq.com/u/lucazamm)\
**Post date:** [February 19, 2019, 9:46pm UTC](https://discuss.konghq.com/t/docker-compose-load-configuration/2849/1 "2019-02-19T21:46:33Z")

</div>

Hi to All,  
first of all I want to thank to the community and Kong Nation!

I am trying Kong in these days, and I would like to start Kong with docker compose.

My question is: how could I load services, consumers and routes configurations after kong startup ? The only way is to use a database dump or a script with REST Api ?

Thanks to all.

Best  
Luca

---

<div class="post-metadata">

**Author:** ![jeremyjpj0916](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/jeremyjpj0916/32/1388_2.png) [@jeremyjpj0916](https://discuss.konghq.com/u/jeremyjpj0916)\
**Post date:** [February 21, 2019, 4:48am UTC](https://discuss.konghq.com/t/docker-compose-load-configuration/2849/2 "2019-02-21T04:48:01Z")

</div>

The Admin API that is exposed on port 8001 by default is a good way to give Kong a go:

> **[Open-Source API Management and Microservice Management](https://docs.konghq.com/1.0.x/admin-api/)**
>
> Secure, Manage & Extend your APIs or Microservices with plugins for authentication, logging, rate-limiting, transformations and more.

And when you want something more visual I recommend Konga as a tool to see your Kong gateway and configure options without doing programmatic calls all the time:

> **[pantsel/konga](https://github.com/pantsel/konga)**
>
> More than just another GUI to Kong Admin API. Contribute to pantsel/konga development by creating an account on GitHub.

---

<div class="post-metadata">

**Author:** ![lucazamm](https://avatars.discourse-cdn.com/v4/letter/l/9fc29f/32.png) [@lucazamm](https://discuss.konghq.com/u/lucazamm)\
**Post date:** [February 21, 2019, 8:56pm UTC](https://discuss.konghq.com/t/docker-compose-load-configuration/2849/3 "2019-02-21T20:56:42Z")

</div>

Thanks Jeremy,  
I used Konga in these last days.

I think the only way is to develop a Java project with API calls and settings called after Kong docker execution.

Bye  
Luca

---

<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…