<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>devcontainer</title>
    <link rel="self" type="application/atom+xml" href="https://links.biapy.com/guest/tags/1978/feed"/>
    <updated>2026-05-31T17:08:22+00:00</updated>
    <id>https://links.biapy.com/guest/tags/1978/feed</id>
            <entry>
            <id>https://links.biapy.com/links/1414</id>
            <title type="text"><![CDATA[vscli]]></title>
            <link rel="alternate" href="https://github.com/michidk/vscli" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/1414"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[A CLI/TUI that simplifies launching VSCode projects, with a focus on dev containers.]]>
            </summary>
            <updated>2025-08-28T19:52:13+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/4409</id>
            <title type="text"><![CDATA[Lapdev]]></title>
            <link rel="alternate" href="https://lap.dev/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/4409"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[Self-Hosted Remote Development Environment.

Open source, self hosted with ease. It uses Devcontainers spec and scales from a single machine to a global fleet of servers.

Lapdev is a self hosted application that spins up remote development environments on your own servers or clouds. It scales from a single machine in the corner to a global fleet of servers. It uses Devcontainer open specification for defining your development environment as code. If you’re interested in a deep dive into how Lapdev works, you can read about its architecture here.

- [Lapdev @ GitHub](https://github.com/lapce/lapdev).]]>
            </summary>
            <updated>2025-08-29T04:11:26+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/5515</id>
            <title type="text"><![CDATA[Development containers]]></title>
            <link rel="alternate" href="https://containers.dev/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/5515"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[An open specification for enriching containers with development specific content and settings. 

A Development Container (or Dev Container for short) allows you to use a container as a full-featured development environment. It can be used to run an application, to separate tools, libraries, or runtimes needed for working with a codebase, and to aid in continuous integration and testing. Dev containers can be run locally or remotely, in a private or public cloud.

- [Development Containers @ GitHub](https://github.com/devcontainers/spec).

Related contents:

- [Utilisation des DevContainer @ DevSecOps :fr:](https://blog.stephane-robert.info/docs/developper/autres-outils/ide/visual-studio-code/devcontainers/#pourquoi-utiliser-devcontainers-avec-vscode).
- [Run Your Project in a Dev Container, in Zed @ Zed blog](https://zed.dev/blog/dev-containers).]]>
            </summary>
            <updated>2026-01-19T06:47:33+00:00</updated>
        </entry>
    </feed>
