coder VS devstream

Founder of coder (https://github.com/coder/coder) here. We choose Terraform as our provisioning layer so that users can provision full blown VMs as their development environment.

We have many teams using GPUs with Coder for ML workloads but doing GUI/Game remote development where interactivity is essential remains elusive.

If you're looking for a collaboration tool, try Coder.

You're right, Tailscale is not 100% open source but the clients and DERP system being open source is enough for you to create what is requested here. A perfect example is https://github.com/coder/coder

Coder is using SQLc. You are responsible for handling transactions, see this example:

The company i work for is planning on implementing Coder ( GitHub - coder/coder: A tool that provisions remote development environments via Terraform) with VS Code.

Next, you'll need a workspace template to be able to create a workspace. Again, the Coder's docs explain how to do this well and there is an example k8s template you can start from.

Coder https://github.com/coder/coder

:wave: Hey, Geoff here from Coder (https://github.com/coder/coder). I used to work at Gitpod. There's a bigger thing more folks should be paying attention to and that's VSCode, and what the purpose of VSCode is. To turn the world into consumers of Microsoft Azure via GitHub. See https://ghuntley.com/fracture.

About nine months ago, DevStream was first publicly released. Since then, it has evolved a lot. If this is the first time you have come across DevStream, maybe read this blog for a quick overview.

DevStream Source Code Repository

Hacktoberfest by Digital ocean always excites the Open source community at large. In this 2022 edition, Apache DevLake and CNCF DevStream projects are participating in Hacktoberfest. Our goal is to enable contributors to learn and grow together with the community.

See the full changelog here.

This is Tiexin Guo, DevStream PMC Chair (an open-source DevOps project with an enthusiastic community.)

@aeinrw made their first contribution in https://github.com/devstream-io/devstream/pull/456

I’ve been working as a DevOps engineer since 2016, and as of today in 2022, I'm still working on it (as the PMC of DevStream). In 2021, I was lucky enough to join AWS as a Senior (L6) DevOps (already left, though). But this article doesn’t represent AWS’s view; nor does it represent my current corporate view. It’s my personal opinion, which I learned and formulated over the years of hands-on experience in projects.

If you are intrigued by the simplicity of "DevOps toolchain as code", don't hesitate to check out DevStream here.