That’s how I did it as well. Webpack as a separate service. I actually used your repo as inspiration.
egze
cnck1387
Ah cool. Things are much different now than that repo (using a single multi-stage build instead of 2x Dockerfiles). I was going to update it once I get deployment covered.
0
egze
Oh wow, looking forward to the update. Could you maybe give a sneak preview on the Dockerfile for dev? Really need it right now 
0
NobbZ
Well every one to what they like, but for me it’s nothing I could get speed with… Constantly needing to rebuild the container slows me down.
0
egze
Thanks! I’ll try to get through it tomorrow.
This caused problems with my VSCode + ElixirLS extention. It could not find the deps location and highlighted the whole mix.exs file red. I tried to write the deps and _build to the original default location, but that causes problems apparently.
0
cnck1387
Weird. I tried VSCode, ElixirLS and remote containers and everything was found with the custom paths using that exact Docker set up. Autocomplete worked, linting worked, etc.. It was pretty sweet.
It all worked out of the box mostly. I loosely followed this guide: https://ilhub.io/blog/2019/05/30/vscode-remote
Some stuff is out of date in that blog post (menu names) , but the general steps worked.
1
egze
Yes, with remote containers. But I don’t use remote, because it required vscode insiders. Or it’s possible with normal vscode now?
0
cnck1387
When I used VSCode I only ever ran insiders. I’m not sure if it’s available in the stable release, but honestly, insiders was quite stable. I used it for like 6 months for hardcore every day development and it never crashed once.
0
egze
egze
Btw, did you ever encounter that yarn install needs phoenix and phoenix_html deps that come from mix? I don’t see how you dealt with it.
0