# Having a local "Serve" option

**URL:** <https://community.doppler.com/t/having-a-local-serve-option/526>\
**Category:** Feature Requests\
**Created:** [February 20, 2022, 3:29pm UTC](https://community.doppler.com/t/having-a-local-serve-option/526 "2022-02-20T15:29:55Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![anon88019548](https://avatars.discourse-cdn.com/v4/letter/a/b19c9b/32.png) [@anon88019548](https://community.doppler.com/u/anon88019548)\
**Post date:** [February 20, 2022, 3:29pm UTC](https://community.doppler.com/t/having-a-local-serve-option/526/1 "2022-02-20T15:29:55Z")

</div>

When writing an application/service that consumes your API for downloading secrets (instead of serving via `doppler run`) it would be great for disconnected scenarios if there were an “official” solution so serve the API endpoint for downloading secrets, from a fallback file. Either via the Doppler CLI or a Docker image that could be used as a side-car.

```auto
doppler serve .doppler/doppler.encrypted.json

```

Currently solving this myself, by having a configuration API, that has one endpoint behaving the same as the official download secrets endpoint. This API is then started via `doppler run --fallback ...`. Then this application is used internally over HTTPS, as a way to configure applications with secrets during boot.

I could use `doppler run` in all those services, but, when developing in .NET, using `doppler run` makes the debug experience somewhat harder. I therefore use a .NET configuration provider that works against your API. Works great. But when it comes to a “disconnected only” required environment, it would be great to be able to point to a locally served endpoint so that you could have the same application code running independent of environment.

---

<div class="post-metadata">

**Author:** ![dejvid-smth](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/dejvid-smth/32/486_2.png) [@dejvid-smth](https://community.doppler.com/u/dejvid-smth)\
**Post date:** [July 25, 2022, 1:12pm UTC](https://community.doppler.com/t/having-a-local-serve-option/526/2 "2022-07-25T13:12:10Z")

</div>

Yes please. I was looking for exactly this feature for .Net project as well.

This would also reduce API calls to Doppler during local development a lot.