#devcontainer — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #devcontainer, aggregated by home.social.
-
Question for #devcontainer experts: should the container stop when you exit the editor/IDE? Or when you close the project in the editor/IDE? Or neither, and it just stays running? (If it matters, I'm using @zed.)
-
Question for #devcontainer experts: should the container stop when you exit the editor/IDE? Or when you close the project in the editor/IDE? Or neither, and it just stays running? (If it matters, I'm using @zed.)
-
OK, I have created my own #devcontainer image and I have started testing it with @zed using a small project. So far, so good.
-
OK, I have created my own #devcontainer image and I have started testing it with @zed using a small project. So far, so good.
-
Claude Code入りのDockerイメージをDevContainerで動かす
https://qiita.com/sour23/items/a86a42a675e27853299b?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items -
I just pushed my #ros2 #devcontainer to #codeberg using rootless #podman
-
【VSCode】devcontainerでCodex認証が通らない？ ポート1455を巡る「椅子取りゲーム」の制し方
https://qiita.com/cojicoji136/items/ce5b5806f6d9e3175b93?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items -
🎉 My New #HomeAssistant Integration Blueprint is live!
Modern template for custom integrations with:
✅ 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! 🚀
👉 https://github.com/jpawlowski/hacs.integration_blueprint
#HomeAutomation #IoT #SmartHome #OpenSource #Python #AsyncIO #HACS #VSCode #Docker
-
🎉 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.
-
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.
-
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
-
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.
-
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?
-
What's your position to working (software developing) within a #devcontainer environment?
-
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 conveniencehttps://www.tay-tec.de/en/blog/zed-devcontainer-ssh/index.html
-
Docs as Code: Наш опыт документирования с LaTeX и Dev container
В мире разработки мы постоянно сталкиваемся с технической документацией — она повсюду, от спецификаций API до архитектурных решений. И мы хотим, чтобы документация была структурированной, актуальной и удобной… но в реальности чаще имеем дело с хаотичным набором разрозненных материалов, которые теряются между Confluence, почтой и Google Docs, стремительно устаревают и выглядят небрежно, с «плывущими» таблицами и запутанной структурой. Представили этот беспорядок? Хорошая новость: есть способ автоматизировать и стандартизировать документацию, сделав её такой же управляемой, как код — через модель docs as code . В статье вместе вспомним базовые принципы этого подхода, расскажем про наш опыт документирования и поделимся репозиторием с готовым шаблоном LaTeX для максимально быстрого старта без установки зависимостей!
https://habr.com/ru/articles/931034/
#Документация #latex_шаблон #docsascode #devcontainer #автоматизация_документации #devcontainer_для_latex #cicd_для_pdf #latex_для_начинающих
-
Setting up #devcontainer for my #LeetCode playground repo, help me Cthulhu
-
Setting up #devcontainer for my #LeetCode playground repo, help me Cthulhu
-
2025年版Elixir×VSCode×コンテナで始めるお手軽環境構築
https://qiita.com/misohagi/items/d8e3e80f6f22c042a33c?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items -
企業でCline導入のために開発環境をコンテナ化し，セキュリティ対策を考える #devcontainer
https://qiita.com/sigma_devsecops/items/623eefcb95edc26a965a?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items -
It would be hard for me to overstate how much I love pgweb (https://github.com/sosedoff/pgweb). It's a single executable web-based Postgres client that’s feature rich, simple, fast and super lightweight. It pairs nicely with my DevContainer for poking around the DB in the container. #postgres #development #devcontainer
-
Long time without writing on my blog, let's talk about Dev Containers this time.
DevContainers: Migrating my entire Rust setup - https://www.edu4rdshl.dev/posts/devcontainers-migrating-my-entire-rust-setup/
-
Long time without writing on my blog, let's talk about Dev Containers this time.
DevContainers: Migrating my entire Rust setup - https://www.edu4rdshl.dev/posts/devcontainers-migrating-my-entire-rust-setup/
-
I've been struggling with getting a larger .NET Project to open in a DevContainer. Specifically, the language server kept dying and I was always too busy to figure out why.
It was running out of memory!
Docker on my dev machine had a max memory allocation of 8GB and limited swap. Cranking that up and everything is lovely!
Why didn't I catch this earlier?!
-
Just past month I consulted a company, and I said they shouldn't renew #JetBrains, and fully transition to #VSCode and Coder.
Past week they did. They took three days to replicate their development environment, and a week to move from their muscular memory.
Nothing against JetBrains, but their products feel like 2005 crap on 2015 interfaces and 2025 promises.
#IDE #Programming #Technology #Containers #DevContainer #RemoteDevelopment #JavaScript #JS #PHP #Rust #Go #C #Node #nuxt
-
Just past month I consulted a company, and I said they shouldn't renew #JetBrains, and fully transition to #VSCode and Coder.
Past week they did. They took three days to replicate their development environment, and a week to move from their muscular memory.
Nothing against JetBrains, but their products feel like 2005 crap on 2015 interfaces and 2025 promises.
#IDE #Programming #Technology #Containers #DevContainer #RemoteDevelopment #JavaScript #JS #PHP #Rust #Go #C #Node #nuxt
-
Giving this #Emacs (/ #DoomEmacs ) #devcontainer config a go, so far it's working surprisingly well. I hope I can completely ditch #VSCode with it, at least for most tasks.
Edit: well, there is this bug: https://github.com/doomemacs/doomemacs/issues/6079
https://github.com/nohzafk/emacs-devcontainer -
Giving this #Emacs (/ #DoomEmacs ) #devcontainer config a go, so far it's working surprisingly well. I hope I can completely ditch #VSCode with it, at least for most tasks.
https://github.com/nohzafk/emacs-devcontainer -
My beef with #PHPStorm is not unfounded.
I still believe it wasn't made with Containers in mind and the codebase is "patched" to work with containers.
I've seen two workplaces pivoting to containers and VSCode. Their developers just abandoned #JetBrains for this same reason. Container workflows suck and it's full of inconveniences.
#Programming #SoftwareDevelopment #ContainerDevelopment #DevContainer #Container #OCI #Docker #Podman #PHPStorm #WebStorm #VSCode #WebDevelopment #WebDev
-
My beef with #PHPStorm is not unfounded.
I still believe it wasn't made with Containers in mind and the codebase is "patched" to work with containers.
I've seen two workplaces pivoting to containers and VSCode. Their developers just abandoned #JetBrains for this same reason. Container workflows suck and it's full of inconveniences.
#Programming #SoftwareDevelopment #ContainerDevelopment #DevContainer #Container #OCI #Docker #Podman #PHPStorm #WebStorm #VSCode #WebDevelopment #WebDev
-
Damn, #Fleet doesn't support remote #PHP interpreter.
Guess I'll have to juggle around #PHPStorm while they get their shit together around DevContainers.
Meanwhile, I'm hoping #Zed catches up. As soon it brings the important bits from PHPStorm, I'm moving on.
#JetBrains #Development #SoftwareDevelopment #AppDavelopment #WebDev #WebDevelopment #Containers #Container #Docker #OCI #DevContainer #DevContainers #IDE #Programming
-
Damn, #Fleet doesn't support remote #PHP interpreter.
Guess I'll have to juggle around #PHPStorm while they get their shit together around DevContainers.
Meanwhile, I'm hoping #Zed catches up. As soon it brings the important bits from PHPStorm, I'm moving on.
#JetBrains #Development #SoftwareDevelopment #AppDavelopment #WebDev #WebDevelopment #Containers #Container #Docker #OCI #DevContainer #DevContainers #IDE #Programming
-
Not renewing my #PHPStorm subscription. I'll do once #DevContainer support is as good as #VSCode.
#Programming #PHP #JetBrains #JAVA #Docker #Container #Podman #OCI #Containers #Technology #IDE #AppDevelopment #WebDevelopment #WebDev #Development #SoftwareDevelopment
-
Not renewing my #PHPStorm subscription. I'll do once #DevContainer support is as good as #VSCode.
#Programming #PHP #JetBrains #JAVA #Docker #Container #Podman #OCI #Containers #Technology #IDE #AppDevelopment #WebDevelopment #WebDev #Development #SoftwareDevelopment
-
All the "standard" (#postgres and #rabbitmq ) #docker nodes get up without a problem.
The first #devcontainer also gets up (ok, tuning all the appropriate files might get a bit tricky)
But, building a second #devcontainer always fails, at least with #vscode 1.95.3.
It doesn't matter which #devcontainer I build first, the next one cannot be built. I'll skip copy-pasting the error here -
All the "standard" (#postgres and #rabbitmq ) #docker nodes get up without a problem.
The first #devcontainer also gets up (ok, tuning all the appropriate files might get a bit tricky)
But, building a second #devcontainer always fails, at least with #vscode 1.95.3.
It doesn't matter which #devcontainer I build first, the next one cannot be built. I'll skip copy-pasting the error here
