# Docker Dev Environment (VSCode)

**URL:** <https://forum.elixirforum.com/t/docker-dev-environment-vscode/34907>\
**Category:** Discussions\
**Tags:** docker, dev-environment\
**Created:** [October 13, 2020, 4:14am UTC](https://forum.elixirforum.com/t/docker-dev-environment-vscode/34907 "2020-10-13T04:14:22Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Sanjibukai](https://forum.elixirforum.com/letter_avatar_proxy/v4/letter/s/ecd19e/32.png) [@Sanjibukai](https://forum.elixirforum.com/u/Sanjibukai)\
**Post date:** [October 13, 2020, 2:39pm UTC](https://forum.elixirforum.com/t/docker-dev-environment-vscode/34907/2 "2020-10-13T14:39:48Z")

</div>

Thanks for sharing..

Just to mention that, you could also provide a top level `.env` file and put the following:

```elixir
COMPOSE_PROJECT_NAME=whatever

```

Now you can decouple your project directory structure from what’s docker-compose is using by default..

Also, Since you’re using it within VSCode when you first spin up the devcontainer (`open in container`) you can perform `mix ecto.setup` manually (the first time or as many times as needed after some migrations for example). So I’m not sure if it’s necessary to have it in the command section of your compose file.

Also if you have some equivalent for production, don’t hesitate to share them too 😉

---

_[View the full topic](https://forum.elixirforum.com/t/docker-dev-environment-vscode/34907)._