---
title: "Comment by Lavadera Ruttinger on \"How to Set Up Full-Stack XM Cloud Local Development for Multiple Code Bases\" | Hashnode"
description: "Great breakdown of XM Cloud’s local dev setup! One best practice I’d suggest is to use a consistent .env file pattern across sites to manage hostname and port o"
url: "https://hashnode.com/posts/xm-cloud-local-development-setup/67e4e1b34cbfa0bed1f08888/comment/69f89d4fa6f8d74aeb21286d"
---

[Discussion](https://hashnode.com/posts/xm-cloud-local-development-setup/67e4e1b34cbfa0bed1f08888)

Comment [How to Set Up Full-Stack XM Cloud Local Development for Multiple Code Bases](https://hashnode.com/posts/xm-cloud-local-development-setup/67e4e1b34cbfa0bed1f08888)

[Lavadera Ruttinger](https://hashnode.com/@ruttinger)

[May 4](https://hashnode.com/posts/xm-cloud-local-development-setup/67e4e1b34cbfa0bed1f08888/comment/69f89d4fa6f8d74aeb21286d)

Great breakdown of XM Cloud’s local dev setup! One best practice I’d suggest is to use a consistent `.env` file pattern across sites to manage hostname and port overrides—this makes it much easier to switch between projects without hunting down configs. Also, don’t forget to align your local Docker hostnames exactly with the Sitecore instance’s bindings to avoid those frustrating CORS or redirect loops.