Teh #AzureDeveloperCLI `azd` has been available for a short while as a #devcontainer feature, which I recently used in https://github.com/heaths/azcrypto: https://github.com/heaths/azcrypto/pull/63/files#diff-24ad71c8613ddcf6fd23818cb3bb477a1fb6d83af4550b0bad43099813088686R8

It will not only install `azd`, but the #Azure dev extension for #VSCode. It makes deploying resources and applications a breeze.

I use it in azcrypto in lieu of the resource provisioning scripts I originally wrote for all of #AzureSDK to deploy resources uniformly. This is a publicly available (near) equivalent.

チームで開発するならDev Containersで環境構築工程をスキップしませんか？
https://qiita.com/nikawamikan/items/74e9a561e2d07feb8566?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items
#qiita #環境構築 #Docker #VSCode #devcontainer

เพิ่งรู้ตัวว่าไม่รู้จะดิ้นรนหาทาง setup #Docker|#Podman #Desktop ไปทำไมในเมื่อกดดูจาก VSCode ได้อยู่แล้ว แถมดูแบบ remote ข้ามไปทั้ง #WSL, remote และ #devcontainer ได้หมดเลยด้วย

📝 "A Dev Container for SQLAlchemy with SQLTools"

👤 Pamela Fox (@pamelafox)

🔗 http://blog.pamelafox.org/2023/05/a-dev-container-for-sqlalchemy-with.html

#pyladies #python #devcontainer

📝 "Providing feedback on the VS Code Python experience"

👤 Pamela Fox (@pamelafox)

🔗 http://blog.pamelafox.org/2023/06/providing-feedback-on-vs-code-python.html

#pyladies #python #devcontainer #vscode

#DevContainer #VSCode forwardPort variable - please Vote for implementation - thank you! https://github.com/microsoft/vscode-remote-release/issues/8426

#yakshave:

Installing the #vscode #Python (or Pylance) extension in a #devcontainer will crash the remote extension host without any useful log message if my #colima container is on `aarch64` (a.k.a `arch: host` in colima config). Switched to `x86_64`, and the problem seems to have resolved.

Glad I noticed the architecture and guessed about the fix. Couldn’t find any useful info from the logs. I did find this after resolving it myself: https://github.com/microsoft/vscode-python/issues/8758#issuecomment-558353708

Maybe this will help you…

Ich wollte eben mal #devcontainer ausprobieren, aber irgendwie krieg ich das unter #Manjaro nich so richtig zum Laufen. Da die Pacman-Variante OSS ist, hab ich "code" als #Snap installiert. Der Sample Container von https://code.visualstudio.com/docs/devcontainers/tutorial hat auch funktioniert, aber wenn ich jetzt bspw. https://github.com/mastodon/mastodon versuche darin zu öffnen wirft er direkt ne Fehlermeldung. Hat da jmd ne Idee? Die Fehlermeldung ist leider nicht sehr hilfreich und die Debug-Logs sagen auch nichts aus.

i'm at the point now where it feels kind of icky to run #vscode directly on my machine.

i want a #devcontainer around the things - so it doesn't interact with whatever broken combination of libraries, files and environment-variables my computer has.

#Docker Desktop default setting on Mac is to use only 2GB memory… turns out if you have a #VSCode #devcontainer that runs some JS/TS and a couple other things, that container alone easily uses >2GB memory. It’ll generate enormous CPU load and disk read/write stats, together with yoyo-ing memory usage as it tries to restart language services over and over. Raise Docker’s memory limit (https://docs.docker.com/desktop/settings/mac/) and all this goes away at once. Resource defaults on Windows are similar, check it out!

Before starting #geospatial #development we need to setup a new #programming environment.
For beginners I will suggest you to create a new #devcontainer to use in Visual Studio Code which leverages #Python and #Docker. Let's see how!
https://youtu.be/VHZqBxynvZI

I wrote this Medium article. I wanted a lighter weight "dev/play" mastodon environment. https://medium.com/@happyday.mjohnson/exploring-mastodon-a-beginners-journey-through-the-mastodon-codebase-455e2fd8de94 #mastodon #code #devcontainer #medium

Next blog post releasing this week uses a #devcontainer to showcase #gardenio in #remocal and fully remote dev environments (where both dev env and deployment target are remote). Lots of fun ideas here. Holistic, portable homes for tools is a lever for collaboration across teams, whether you're on macOS, or Windows (well #wsl2) or Linux

Getting @crystalLanguage up and running wasn't as easy as I'd hoped (mostly because of missing dependencies). So, I've created a #vscode #devcontainer that installs all the dependencies and installs #Crystal on a #containerised #Ubuntu development environment.

This all lives in a repo that also contains copies of the Getting Started examples from the official docs.

https://github.com/martinpeck/crystal-playground

A fun little bit of #oss hacking tonight! #docfx released a new version that runs as a #dotnet global tool. I was able to update the #nunit docs docfx-action #github action to drastically simplify it. It now is based on the #dotnet #ubuntu container with a small tool install. Then I updated the NUnit docs #devcontainer to be based on that, plus our node tooling.

Simpler, faster, nicer. Feels good.

If you use a #vscode #devcontainer, and also use @tectonic’s mcfly, I just pushed an update my devcontainer feature that pulls the fix for mcfly crashing when it’s history file isn’t explicitly set.

https://github.com/ChristopherMacGown/devcontainer-features/pkgs/container/devcontainer-features%2Fmcfly

Me, describing the #devcontainer I just had to build: I had to do a lot of things that I didn’t love

I've finally cracked how to use SSH keys from a #devcontainer in #vscode ! https://tom01098.github.io/2022/12/05/devcontainer-ssh.html

for anyone interested in getting #mastodon @joinmastodon running in a dev env using #vscode #devcontainer I've posted a rough set of instructions here: https://babyprogrammer.com/blog/getting-mastodon-up-and-running-with-visual-studio-code-devcontainers/

I wrote a post a few months ago on adding #devcontainer features which did not age very well 😅 Revisited the topic here to show how you can easily add #azure cli extensions and #azurebicep to your #devcontainers using the new #azurecli feature https://dev.to/azure/re-visiting-dev-container-features-205i