#Devcontainer
Exciting!
Getting the #RubyLSP #VSCode extension working in a #DevContainer with the #rv #Ruby version manager is a little fiddly.
The least amount of configuration that I can figure out is a configuration like this:
```
"customizations": {
"vscode": {
"extensions": [
"Shopify.ruby-lsp"
],
"settings": {
"rubyLsp.customRubyCommand": "PATH=$(rv ruby dir)/ruby-3.3.10/bin:${PATH}",
"rubyLsp.rubyVersionManager.identifier": "custom"
}
}
}
```
https://shopify.github.io/ruby-lsp/version-managers.html#custom-activation
Does anyone know how to setup a #devcontainer for #Android development with #dotnet and #JetbrainsRider ?
I can get the container running, and build the project, but can't get the emulator to work to add a virtual device, nor make my physical phone show in the devices panel.
#DevContainer 無いから困ると思ってたけど実は組み込みで存在していたのか。さらなる強化に今後期待。 #Antigravity
https://dev.classmethod.jp/articles/dont-forget-to-use-devcontainer-when-using-antigravity/
#DevContainer 無いから困ると思ってたけど実は組み込みで存在していたのか。さらなる強化に今後期待。 #Antigravity
https://dev.classmethod.jp/articles/dont-forget-to-use-devcontainer-when-using-antigravity/
🎉 My New #HomeAssistant Integration Blueprint is live!
Modern template for custom integrations with:
✅ GitHub Copilot and generic AI agent assisted development
✅ Config flow, coordinator, multiple entity types
✅ #Python 3.13 + async patterns
✅ Full test setup with pytest
✅ #DevContainer for instant setup
✅ #GitHubCodespaces ready (60h/month free!)
✅ Core-aligned tooling (Ruff, Pyright)
Perfect for creating HACS integrations! 🚀
I enjoy setting up a development container at the start of a new project. It takes a bit more time upfront, but then I can work on any of my projects on any machine without having to do toolchain setup all over again. This time it's getting the #RaspberryPi Pico SDK set up with all required build tools. It probably already exists somewhere, but I like building my own.
One downside of Atomic Linux: Helix doesn’t support devcontainers
.devcontainer.json giúp đơn giản hóa việc thiết lập môi trường phát triển cho các dự án cũ hoặc phức tạp. Cộng đồng mã nguồn mở có thể đánh giá cao những đóng góp này vì nó giúp người mới dễ dàng tham gia hơn.
#opensource #devcontainer #lập_trình #mã_nguồn_mở
https://www.reddit.com/r/opensource/comments/1ooamy4/is_devcontainerjson_suitable_pr_material/
Spitballing.. Combining a #DevContainer and #bootc bootable container could make for a neat #LinuxKernel development workflow. Use the former to run the build process and spit out an rpm. Use the bootable container to install the rpm and give a bootable VM for testing the kernel. Would be very portable across distros. Might even run on macOS..
Wer kennt sich denn besser als ich mit #docker und #devcontainer aus? Hab ich das halbwegs richtig hingebastelt?
https://git.rollenspiel.monster/RollenspielMonster/ansible_collection/pulls/14
Пишем чат на Rust
Очередной чат, и к тому же на rust?! Да, yet another. И да, в этой статье не будет каких-то новых откровений системного программирования с написанием своего фреймворка для работы со сетью на уровне драйверов или других испытаний. Этот альманах про мой первый опыт в веб-разработке, который может быть полезен для других новичков, ведь тут мы затронем помимо злосчастного rust такие вещи, как devcontainer, REST API, идентификацию-аутентификацию-авторизацию, WebSockets, SSE, юнит и интеграционные тесты, некоторые паттерны, логирование и прочее.
https://habr.com/ru/articles/945042/
#rust #вебразработа #фуллстек #sse #websockets #devcontainer #авторизация #чат #rest_api
The idea is nice, but… The amount of effort you need to put into #devcontainer when your machine is already intended for development doesn’t offset the advantages compared to its disadvantages. Working on the bare metal is not that disadvantaged unless it involves legacy software.
What's your position to working (software developing) within a #devcontainer environment?
Ooh, devpods, great, so now we can all have the same build environment and we know everything just works!
Hmm, what is that you are saying? Obscure compilation errors? What #devcontainer are you using? Oh, no, that's yesterday's #container, you need the one from today! Unless you're in this special branch, then you need the one from two weeks ago. Possibly. Maybe. Just delete all devpods, purge your image cache and rebuild everything from scratch, that'll fix it! You know what, I don't know either, let's just quit and take up gardening.
When you upgrade to VS Code 1.104.x or later, and you're using dev containers, it may fail starting the container when it tries to download the VS Code Server. In that case uninstalling and reinstalling the "Remote Development" extension resolved the issue in my environment. #VSCode #DevContainer
(1/2) One of the challenges when working with containers is the starting cost (i.e., time and effort) of setting up a new development environment when starting a new project.
The following tutorial focuses on efficiently setting up a new Dockerized development environment with minimal time using GitHub repository templates with VScode and the Dev Containers extension.
The tutorial is available on Medium (for paid subscribers):
https://medium.com/p/6193f6d4ecb4
Devcontainers are the reason why I use MS Visual Studio Code despite tracking and feature nudging. An alternative would be ZED, but it only supports remote editing via SSH.
It is possible to integrate SSH into a Docker container. In brief:
- Install openssh-server in the image
- Configuration must allow password authentication
- Prepared ssh config for devcontainer access
- Docker Compose for added convenience
https://www.tay-tec.de/en/blog/zed-devcontainer-ssh/index.html
Любопытный подгон от Саймона: codespace с предустановленной его тулзой llm, работающей через бесплатные GitHub Models
https://simonwillison.net/2025/Aug/13/codespaces-llm/#atom-everything