jeramyRR
Hi all,
I created a small repo that has the basic docker config files needed to have an Elixir docker development environment in VSCode. I was hoping I could get a few eyes on it to test it out to make sure it’s not just a “it works on my machine” thing.
Basically it’s just the config files. The user will need to start a new Elixir or Phoenix Project, copy the files into their new project, and then open the project up in VS Code. VS Code will then automatically create the docker environment for them.
Here is a link to the repo.
https://github.com/jeramyRR/elixir-vscode-docker-env
Comments and criticisms welcome!
Where Next?
Trending in Discussions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Courses that'll move you from confusion to "Aha, now I get it!"
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Bringing learning, work and compliance together since 1987.
Producing high quality Elixir screencasts since 2017.
**Building the future of software with AI, trust, and human connection.**
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
First Post!- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
Sanjibukai
Thanks for sharing..
Just to mention that, you could also provide a top level
.envfile and put the following: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 performmix ecto.setupmanually (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