Earlier quoted context omitted.
There are 3 main differences: 1) DevPod is based on GitHub/Microsoft's devcontainer.json standard while GitPod has their own file format 2) DevPod is client-only more like Terraform where the client creates/manages things directly using cloud credentials vs GitPod is a server-side solution to manage and provision dev workspaces 3) DevPod has a provider concept similar to Terraform that allows you to provision dev env…
Interesting! Might give this a try some time. I occasionally find myself needing a Linux environment, and my primary device is an arm64 mac, I think it could be useful for that. More generally what do you see being the prime use cases?
Show HN: DevPod – Codespaces but Open Source, Client-Only, and Unopinionated
11–20 of 32 posts
Re: Show HN: DevPod – Codespaces but Open Source, Client-Only, and Unopinionated
#12Neat! I enjoyed using gitpod a few times, this seems similar. How do they compare?
There are 3 main differences: 1) DevPod is based on GitHub/Microsoft's devcontainer.json standard while GitPod has their own file format 2) DevPod is client-only more like Terraform where the client creates/manages things directly using cloud credentials vs GitPod is a server-side solution to manage and provision dev workspaces 3) DevPod has a provider concept similar to Terraform that allows you to provision dev env…
Re: Show HN: DevPod – Codespaces but Open Source, Client-Only, and Unopinionated
#13Earlier quoted context omitted.
There are 3 main differences: 1) DevPod is based on GitHub/Microsoft's devcontainer.json standard while GitPod has their own file format 2) DevPod is client-only more like Terraform where the client creates/manages things directly using cloud credentials vs GitPod is a server-side solution to manage and provision dev workspaces 3) DevPod has a provider concept similar to Terraform that allows you to provision dev env…
Are there any plans for an iPadOS client?
Re: Show HN: DevPod – Codespaces but Open Source, Client-Only, and Unopinionated
#14That's very a very good sight the see! Comparable solutions are full of dark patterns on sign up, and I already gave up and decided not to give them any access to any projects. This is a game changer.
Re: Show HN: DevPod – Codespaces but Open Source, Client-Only, and Unopinionated
#15When 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.
Re: Show HN: DevPod – Codespaces but Open Source, Client-Only, and Unopinionated
#16I’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 inter…
Re: Show HN: DevPod – Codespaces but Open Source, Client-Only, and Unopinionated
#17I’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 inter…
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.
Re: Show HN: DevPod – Codespaces but Open Source, Client-Only, and Unopinionated
#18- File sync with the local filesystem and the container (2-way)
- Port-forwarding to localhost for debugging (I guess the DevPod way is to run the entire IDE in the container, but I love Tilt/DevSpace for allowing me to work in my local fat IDE)
Re: Show HN: DevPod – Codespaces but Open Source, Client-Only, and Unopinionated
#19This sounds kind of like Tilt and DevSpace, but for just general purpose containers. From a quick look through the website, I didn't see these features, but these would be great additions: - File sync with the local filesystem and the container (2-way) - Port-forwarding to localhost for debugging (I guess the DevPod way is to run the entire IDE in the container, but I love Tilt/DevSpace for allowing me to work in my…
Re: Show HN: DevPod – Codespaces but Open Source, Client-Only, and Unopinionated
#20Earlier quoted context omitted.
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.
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?