Remote Developer Environments

Remote Developer Environments

Commit 16: Kennt ihr noch #gitpod? Wie einfach und genial war das: [gitpod-url]#[repo-url] Baam... Full-Blown vscode like Editor war im Web startklar. Gefühlt wie #cloudgaming für git-edits.
Das funktioniert leider so nicht ootb mit #forgejo / #codeberg. Aaaber schaut mal #DevPod. Wollen wir bis zum #39c3 vielleicht was für @Codeberg draus machen?
Zum Einstieg die Doku von DevPod:
\__
#jek25 #cccRegio #wartenAuf39c3 #opensource #foss #floss #git @forgejo
#gitpod is apparently going all-in on AI agents for software development. It's a pity, Gitpod used to be a very useful tool. I guess I'll have to go back to installing the ESP toolchain locally for compiling #tasmota
OTOH, I never paid for it, since the free offering was always plenty for my use case, so I don't begrudge them wanting to cash in on the AI bubble before it collapses. They may be a tad late, though...
#Gitpod discontinued using #Kubernetes after six years of use and experimentation.
This decision emerged from their experience managing development environments for 1.5 million users while handling numerous environments daily.
Details on #InfoQ 🔗 https://bit.ly/49WiN84
Am I using #Github #Codespaces wrong?
I thought the point of creating a devcontainer.json file to specify extra bits have built when you set up a machine, and they were honoured on the creation of codespaces.
Given that #Gitpod seems to be adopting #devcontainer now, I figured I'd try Codespaces. A basic thing seems to be harder than I thought.
If you have direct experience building Codespaces, would you share a pointer on how to fix this seemingly basic thing?
https://gist.github.com/mrchrisadams/9ee981ffdcc1cef38431f51a76886098