# Configuring Browsersync inside a ddev (docker) container and make hot realoding work

**URL:** https://discourse.roots.io/t/configuring-browsersync-inside-a-ddev-docker-container-and-make-hot-realoding-work/20004
**Category:** sage
**Tags:** browsersync, sage9
**Created:** 2021-02-03T10:02:13Z
**Posts:** 7
**Showing post:** 2 of 7

## Post 2 by @Atari — 2021-02-03T11:32:10Z

This may help:

> [@Sage 9 on Docker: https://localhost:3000 not working](https://discourse.roots.io/t/sage-9-on-docker-https-localhost-3000-not-working/15334/2):
>
> Can you share your resources/assets/config.json? The devUrl key is what is being proxied by webpack/Browsersync in Sage. You should be setting that to whatever the address for the Nginx container is. Looks like just http://localhost.

The `devUrl` key is what is being proxied by webpack/Browsersync in Sage. You should be setting that to whatever the address for the Nginx container is.

I always run my builds outside my vm (trellis stack).

Windows related thread  
[https://discourse.roots.io/t/browsersync-not-watching-changes-in-docker-for-windows/11275](https://discourse.roots.io/t/browsersync-not-watching-changes-in-docker-for-windows/11275)

---

_[View the full topic](https://discourse.roots.io/t/configuring-browsersync-inside-a-ddev-docker-container-and-make-hot-realoding-work/20004)._