# All-in-one docker compose **URL:** \ **Category:** Uncategorized\ **Created:** [October 7, 2024, 12:27am UTC](https://openziti.discourse.group/t/all-in-one-docker-compose/3206 "2024-10-07T00:27:23Z")\ **Posts on this page:** 1\ **Showing post:** 11
**Author:** ![TheLumberjack](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/thelumberjack/32/113_2.png) [@TheLumberjack](https://openziti.discourse.group/u/TheLumberjack)\ **Post date:** [October 8, 2024, 3:40pm UTC](https://openziti.discourse.group/t/all-in-one-docker-compose/3206/11 "2024-10-08T15:40:07Z")
> [@Trading6165](#): > > As is, if I open 1280 to the world, then the ZAC is exposed as well... IMO, it's entirely fine to start here. I have a couple ZAC instances exposed like [https://ctrl.clint.demo.openziti.org:8441/zac/login](https://ctrl.clint.demo.openziti.org:8441/zac/login). So I don't think there's any harm in having it exposed per-se. Is it better to have it split off an inacessible to the world? sure, but I would **STRONGLY** urge you to get things working with it exposed, understand how things work without splitting the API, then migrate to having it split off. But if you want to start off that way - you can 🙂 If you're interested in a video you can watch [https://www.youtube.com/watch?v=FI4byEDg344](https://www.youtube.com/watch?v=FI4byEDg344) --- _[View the full topic](https://openziti.discourse.group/t/all-in-one-docker-compose/3206)._