[dchuk]

I’m a solo dev, and just last night got a good local docker compose workflow setup for writing rails apps on my m1 Mac using Colima last night.

When I fired it up in vs code, I was immediately presented with all the dev container stuff, and I wasn’t sure what to do next.

I assumed I’d write and store all of my code locally in my Mac, then just use volumes to sync it over and run docker commands on my machine to interact with the app…

Should I use dev containers instead? Should I use dev pods? I want to be able to leave code for a while and come back and easily fire it up, I want simple deploys on single servers when ready (compose or swarm)…but I just keep running into so many options I’m getting confused.

[gentele]

Adding devcontainer.json and then using DevPod with it should be pretty straight-forward for you. You can use docker-compose inside devcontainer.json if you want to reuse your existing setup.

[dchuk]

Well I guess that’s my question then. Does the devpod become part of my docker compose app? Or does it run separately of it?

[gentele]

It's a separate desktop app similar to docker desktop. DevPod is very, very lightweight though.

[dchuk]

Ok, so I’d have this installed, and then Colima, and then vscode, all on my Mac. For the app I’m working on, I’d run it all in its own docker compose setup, I’d have the source code on my Mac (?), and the dev container would house all of the extensions and language servers and linters I need for this app, but in a separate container from my compose setup, and vs code would talk to it?