ycrab

4 ms·

1.
by ycrab 3y ago
Partially, yep. The more important part is that these Docker images run on a remote machine
2.
by ycrab 3y ago
creating the workspace is based on docker but within the workspace you're free to do whatever you want, no need to use docker-compose there
3.
by ycrab 3y ago
If you can script your setup steps, you can also run it in a devcontainer, either by using docker-compose[1] to bake it into the workspace image or using lifecycle hooks to run some scripts after creating the workspace[2] [1] http:/&#x
4.
by ycrab 3y ago
Yep, as we see it they compliment each other quite well. DevPod takes your workspace to the cloud and DevSpace let's you develop against your Kubernetes cluster - potentially the same one you used to start your workspace. Internally we
5.
by ycrab 3y ago
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&
6.
by ycrab 3y ago
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/backe
7.
by ycrab 3y ago
we're thinking about it but don't have any immediate plans. Mostly because it's not a straight forward port and we want to make sure it's stable on linux/windows/macOS before tackling mobile. Would be awesome f
8.
by ycrab 3y ago
Basically anything you'd use GitHub Codespaces for but without having to pay them a hefty fee + you get to choose your cloud provider (or self-hosted k8s). I.e. if you have some left over aws credits, you could start off with that but