Live data from Hacker News

Show HN: DevPod – Codespaces but Open Source, Client-Only, and Unopinionated

github.com

21–30 of 32 posts

Re: Show HN: DevPod – Codespaces but Open Source, Client-Only, and Unopinionated

#21

This 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…

Port-forwarding and using your local IDE is already working in DevPod today. We also added auto-port-forward where it watches what happens inside the container and then starts port-forwarding automagically.

File sync: That is a great idea. We got that in DevSpace already as you mentioned and we definitely think this could be super valuable in DevPod as well. Right now, a git push and then pull is required to get things from inside DevPod updated on local but with sync this would be even easier and faster.

Re: Show HN: DevPod – Codespaces but Open Source, Client-Only, and Unopinionated

#22
post #21

This 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…

Port-forwarding and using your local IDE is already working in DevPod today. We also added auto-port-forward where it watches what happens inside the container and then starts port-forwarding automagically. File sync: That is a great idea. We got that in DevSpace already as you mentioned and we definitely think this could be super valuable in DevPod as well. Right now, a git push and then pull is required to get thin…

We have a designer on the team that uses a Windows box. This could be a great way to get him spun up without having to build him a local setup and manage two sets of local dependencies for him on Windows and us on macOS.

How well does it work for web dev - Django specifically? Is it as simple as running the dev server and accessing the locally-forwarded port through a local browser? Are there any gotchas to be aware of? Thanks!

Re: Show HN: DevPod – Codespaces but Open Source, Client-Only, and Unopinionated

#23
post #21

Earlier quoted context omitted.

Port-forwarding and using your local IDE is already working in DevPod today. We also added auto-port-forward where it watches what happens inside the container and then starts port-forwarding automagically. File sync: That is a great idea. We got that in DevSpace already as you mentioned and we definitely think this could be super valuable in DevPod as well. Right now, a git push and then pull is required to get thin…

We have a designer on the team that uses a Windows box. This could be a great way to get him spun up without having to build him a local setup and manage two sets of local dependencies for him on Windows and us on macOS. How well does it work for web dev - Django specifically? Is it as simple as running the dev server and accessing the locally-forwarded port through a local browser? Are there any gotchas to be aware…

Exactly. add a devcontainer similar to the example repo in [1], install the devpod app and point it to the repository and your designer is good to go, including port forwarding to their localhost

[1] https://github.com/backendclub/example-django-devcontainers

Re: Show HN: DevPod – Codespaces but Open Source, Client-Only, and Unopinionated

#24
post #23

Earlier quoted context omitted.

We have a designer on the team that uses a Windows box. This could be a great way to get him spun up without having to build him a local setup and manage two sets of local dependencies for him on Windows and us on macOS. How well does it work for web dev - Django specifically? Is it as simple as running the dev server and accessing the locally-forwarded port through a local browser? Are there any gotchas to be aware…

Exactly. add a devcontainer similar to the example repo in [1], install the devpod app and point it to the repository and your designer is good to go, including port forwarding to their localhost [1] https://github.com/backendclub/example-django-devcontainers

Thanks! Is it trivial to “copy” container connection information between machines? For example, can I write a devcontainer.json, spin up a back-end on Digital Ocean, make sure it has all the necessary envs and system dependencies and is working correctly, then just copy-paste connection information to that pod and send it to my designer, where he just pastes it into his DevPod desktop app and is off to the races?

Re: Show HN: DevPod – Codespaces but Open Source, Client-Only, and Unopinionated

#25
post #23

Earlier quoted context omitted.

Exactly. add a devcontainer similar to the example repo in [1], install the devpod app and point it to the repository and your designer is good to go, including port forwarding to their localhost [1] https://github.com/backendclub/example-django-devcontainers

Thanks! Is it trivial to “copy” container connection information between machines? For example, can I write a devcontainer.json, spin up a back-end on Digital Ocean, make sure it has all the necessary envs and system dependencies and is working correctly, then just copy-paste connection information to that pod and send it to my designer, where he just pastes it into his DevPod desktop app and is off to the races?

Once you set up the provider on the designers machine, you can embed a deep link to the desktop app in your repo, similar to the „open in devpod“ button in our repo [1]. [1] https://github.com/loft-sh/devpod/blob/main/README.md (See line 11). This makes sure they open the correct repo with the provider you configured and are ready to go

For your use case it’d be cool to share provider information between parties. We‘ll think about it, although that might also be a potential selling point for teams and a commercial product…

Re: Show HN: DevPod – Codespaces but Open Source, Client-Only, and Unopinionated

#26
post #25

Earlier quoted context omitted.

Thanks! Is it trivial to “copy” container connection information between machines? For example, can I write a devcontainer.json, spin up a back-end on Digital Ocean, make sure it has all the necessary envs and system dependencies and is working correctly, then just copy-paste connection information to that pod and send it to my designer, where he just pastes it into his DevPod desktop app and is off to the races?

Once you set up the provider on the designers machine, you can embed a deep link to the desktop app in your repo, similar to the „open in devpod“ button in our repo [1]. [1] https://github.com/loft-sh/devpod/blob/main/README.md (See line 11). This makes sure they open the correct repo with the provider you configured and are ready to go For your use case it’d be cool to share provider information between parties. We‘…

Perfect, thanks for your time. Provider setup + deep link will work fine for us.

Re: Show HN: DevPod – Codespaces but Open Source, Client-Only, and Unopinionated

#27
A bit off topic - but does anyone know of a „pod“-solution with a mobile UI / optimized workflow?

I often find myself wanting to code on an existing project from my phone. Yes, vscode kind of works but it‘s not a quite the experience i‘m looking for.

Re: Show HN: DevPod – Codespaces but Open Source, Client-Only, and Unopinionated

#28
post #20
post #17

Earlier quoted context omitted.

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?

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

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?

Re: Show HN: DevPod – Codespaces but Open Source, Client-Only, and Unopinionated

#30
post #29

This looks like it could be exactly what I have been looking for--nice work! I manage multiple AWS accounts, and my credentials file has multiple profiles in it. When using the AWS provider, is it possible to specify which profile to use?

Hi! For now there is no exposed option for profile-selecting in the AWS Provider You can add multiple instances of the AWS provider and specify token/secret for each of them

But I'll open an issue to investigate how to implement the profile-selection, thanks for the feedback :)

EDIT: implemented

Post reply on HN