# remote-development A software development practice in which developers work with source code, tools, and runtimes hosted on remote machines, containers, or similar environments. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Run Codex in the cloud - DigitalOcean for Codex is now available DevFeed: [Run Codex in the cloud - DigitalOcean for Codex is now available]() Original publisher: [Read original article]() Author: Ari Sigal Published: 2026-06-25T21:16:06Z Content type: release Language: en Sources: [DigitalOcean]() Topics: [codex](), [Digital Ocean](), [remote-development](), [Cloud](), [Provisioning](), [ssh](), [ChatGPT]() Tags: [ai-ml](), [cloud](), [codex](), [digitalocean](), [mobile](), [oauth](), [plugin](), [preview](), [product-updates](), [provisioning](), [remote-development](), [ssh]() ### AI overview DigitalOcean announces a Public Preview plugin for Codex that lets developers provision persistent, Codex-ready cloud development machines in their own DigitalOcean accounts using natural-language prompts. The resulting Droplets include the Codex CLI, common programming-language tooling, and SSH access. ### Source excerpt As your agents are working on more complex, long-running work, they need a clean, persistent environment to keep running. Setting up a persistent remote machine by hand means creating a cloud server, configuring SSH keys, installing dependencies, and wiring everything back to your workflow. It's a lot of infrastructure work before you write a single line of code. Today, we're making that easier. The DigitalOcean plugin for Codex is now available in Public Preview, letting developers create and connect Codex-ready cloud development machines in their own DigitalOcean account directly from within Codex -- using natural language, with no manual setup. This means that not only can your work continue running when you step away, but with Codex in the ChatGPT mobile app you can stay in control -- starting, steering, or monitoring work from wherever you are. What is DigitalOcean for Codex? The DigitalOcean plugin connects your DigitalOcean account to the Codex app, letting you provision a persistent remote development environment on demand. Instead of manually spinning up a server and configuring it, you can ask Codex to do it. The result: a DigitalOcean Droplet® that's pre-configured with the Codex CLI, common programming language tooling (based on the codex-universal Docker image), and SSH access -- so your work can keep running and stay within reach, even when you're not at your desk. How it works Starting from Codex Install the DigitalOcean plugin from the Codex plugin directory. During installation, you'll connect your DigitalOcean account via OAuth -- no API tokens to create or paste. Then prompt: @DigitalOcean create a new remote machine Codex will: Provision a new Droplet from the Codex Droplet template Generate and configure an SSH key on your device Wait for the machine to finish provisioning (and check back automatically when it's ready) Return a deeplink to the Codex SSH connections page to finalize the connection Once connected, you're running Codex on a persistent ## Run Your Project in a Dev Container, in Zed DevFeed: [Run Your Project in a Dev Container, in Zed]() Original publisher: [Read original article]() Author: Danilo Leal, Kyle Barton Published: 2026-01-07T00:00:00Z Content type: tutorial Language: en Sources: [Zed Industries - Blog]() Topics: [Development](), [Containers](), [Docker](), [Infrastructure as code](), [remote-development]() Tags: [container](), [dev](), [development](), [docker](), [how-to](), [infrastructure-as-code](), [json](), [remote](), [ui]() ### AI overview Zed v0.218 adds support for opening projects in Docker-based Dev Containers. The article explains how Dev Containers provide consistent, reproducible development environments and how Zed opens, reconnects to, and works within them. ### Source excerpt Open projects in Docker-based Dev Containers in Zed for consistent, reproducible development environments. ## Enhance productivity with AI + Remote Dev DevFeed: [Enhance productivity with AI + Remote Dev]() Original publisher: [Read original article]() Author: Brigit Murtaugh, Christof Marti, Josh Spicer, Olivia Guzzardo McVicker Published: 2025-05-27T00:00:00Z Content type: article Language: en Sources: [Visual Studio Code - Code Editing. Redefined.]() Topics: [remote-development](), [Visual Studio Code](), [Artificial Intelligence](), [GitHub Copilot](), [Containers](), [Large Language Model](), [ssh](), [Windows Subsystem for Linux]() Tags: [ai](), [ai-coding](), [article](), [blog](), [container-based-application](), [containers](), [copilot](), [dev](), [developer](), [developer-productivity](), [development](), [github](), [github-copilot](), [linux](), [llm](), [productivity](), [remote](), [ssh](), [vs-code](), [windows](), [wsl]() ### AI overview This VS Code article explains how AI, including GitHub Copilot, can enhance Remote Development workflows. It covers contextual chat, remote installation, assistance with setup and debugging, custom instructions, chat participants, tool approvals, and isolated autonomous coding sessions across SSH, Dev Containers, WSL, tunnels, and GitHub Codespaces. ### Source excerpt Enhance your developer productivity with AI and Remote Development. Read the full article ## Migrating from Fauna to Supabase DevFeed: [Migrating from Fauna to Supabase]() Original publisher: [Read original article]() Author: Prashant Sridharan Published: 2025-03-21T07:00:00Z Content type: tutorial Language: en Sources: [Supabase Blog]() Topics: [migration](), [Supabase](), [Databases](), [API](), [SQL](), [JSON](), [Serverless](), [Access Control](), [Authentication](), [GraphQL](), [remote-development](), [TypeScript]() Tags: [database](), [graphql](), [guide](), [json](), [migration](), [open-source](), [real-time](), [security](), [serverless](), [sql](), [typescript]() ### AI overview A guide to migrating from Fauna to Supabase before Fauna sunsets. It compares their database and API capabilities, then outlines exporting Fauna data, importing JSON into Supabase, transitioning API calls, and optimizing the migrated application. ### Source excerpt A guide to migrating from Fauna to Supabase. ## Zed Adds Remote Development Over SSH DevFeed: [Zed Adds Remote Development Over SSH]() Original publisher: [Read original article]() Author: Conrad Irwin Published: 2024-10-30T00:00:00Z Content type: article Language: en Sources: [Zed Industries - Blog]() Topics: [remote-development](), [ssh](), [Development]() Tags: [architecture](), [cloud](), [collaboration](), [development](), [linux](), [machine](), [projects](), [protocol](), [rebuilds](), [remote](), [remote-development](), [server](), [ssh](), [synchronization](), [tests]() ### AI overview Zed adds remote development over SSH, keeping the user interface local while running language servers, tasks, and terminals on the remote machine. The article explains connection maintenance, remote server installation and compatibility, reconnection behavior, local backups, and collaboration support. ### Source excerpt Zed can now be used to edit over SSH. ## Evolution of Developer Productivity at Square - Part Two DevFeed: [Evolution of Developer Productivity at Square - Part Two]() Original publisher: [Read original article]() Author: Korhan Bircan Published: 2024-01-29T09:00:00Z Content type: article Language: en Sources: [Square Corner Blog RSS Feed]() Topics: [code productivity](), [build times](), [Android](), [remote-development](), [Continuous integration](), [Optimization](), [Caching](), [Gradle](), [Amazon EC2](), [ide](), [benchmarking]() Tags: [android](), [benchmarking](), [build-times](), [caching](), [cloud](), [continuous-integration](), [developer-productivity](), [development](), [engineering](), [gradle](), [ide](), [optimization](), [remote-development](), [velocity]() ### AI overview Square describes efforts to improve developer productivity and development velocity by reducing build, installation, IDE synchronization, and continuous integration times. The article reports development apps, remote Android development environments, configuration caching, CI shard skipping, emulator optimization, Gradle changes, and modularization work. ### Source excerpt Accelerating development velocity ## Bringing Postgres to Bunnyshell with Neon DevFeed: [Bringing Postgres to Bunnyshell with Neon]() Original publisher: [Read original article]() Author: Nikita Shamgunov Published: 2023-03-30T13:38:29Z Content type: article Language: en Sources: [Blog -- Neon Docs]() Topics: [Developer Platform](), [Databases](), [remote-development](), [Database](), [Provisioning](), [Testing]() Tags: [case-studies](), [cloud](), [core](), [database](), [databases](), [developer-platform](), [development](), [productivity](), [provisioning](), [remote-development](), [testing]() ### AI overview Bunnyshell integrates Neon Postgres into its cloud-first Environment-as-a-Service platform, enabling on-demand development environments and ephemeral staging and QA environments. Neon provides near-instant provisioning, populated databases, branching for isolated production-like databases, and automatic scaling for short-lived environments. ### Source excerpt Bunnyshell is a cloud-first developer platform that enables teams to effortlessly create on-demand environments for development, as well as ephemeral environments for staging and QA. Their platform enables engineering teams to focus on building core product features rather than s... ## What's new in Svelte: February 2023 DevFeed: [What's new in Svelte: February 2023]() Original publisher: [Read original article]() Author: Dani Sandoval Published: 2023-02-01T00:00:00Z Content type: release Language: en Sources: [Svelte blog]() Topics: [Svelte](), [remote-development](), [vs-code]() Tags: [releases](), [svelte](), [updates]() ### AI overview This February 2023 update covers Svelte and SvelteKit releases, bug fixes, new features, remote development support, and improvements to the Svelte extension and language tools. ### Source excerpt Since last month, we've seen a couple of minor versions across Svelte and SvelteKit, a bunch of educational content to support the 1.0 release, as well as the State of JS survey results... Svelte, once again, increased in satisfaction and interest, so thanks to everyone who voted! Let's dive into the updates... What's new in SvelteKit Work in the Svelte ecosystem this month has been focused on SvelteKit bug fixes and addressing feedback from the 1.0 launch. One of the more awaited bug fixes to SvelteKit's base path support landed, which means that you can now create SvelteKit projects on remote development environments. There have been several new releases with these fixes as well as a handful of new features such as: The submitter's value will now be included automatically when progressively enhancing (1.0.3, #8273) Added an error in dev mode if global fetch is used with relative URL (1.0.8, #8370) A warning will now indicated that hydration may break if comments are removed from HTML (1.0.11, #8423) A warning will occur when of page options are used in .svelte files or a missing in layout is detected (1.1.0, #8475) The new text(...) helper makes it easy to generate text responses (1.2.0, #8371) The public env can now be accessed within app.html (1.2.0, Docs, #8449) An error will now be thrown if cookie exceeds size limit (1.2.1, #8591) The generated tsconfig can now be modified (1.3.0, #8606) What's new in Svelte and Language Tools Added support for html.customData from the VS Code HTML language service (extensions-107.0.0, #1824) Autocompletion for stores that need to be imported (#1823) and object/class member snippets (#1817) has been added to the Svelte extension (extensions-107.0.0) Improve detection of promises that are also functions (Svelte 3.55.1, #8162) Add missing types and properties for the global part attribute and on:submit, respectively (Svelte 3.55.1, #8181) Lots of performance and bug fixes (Svelte 3.55.1* and extensions-107.0.x) *for al ## Remote Software Development - Lessons Learned DevFeed: [Remote Software Development - Lessons Learned]() Original publisher: [Read original article]() Author: umer Published: 2016-06-12T00:00:00Z Content type: article Language: en Sources: [Code Ahoy - Articles]() Topics: [remote-development](), [Development](), [Code](), [modules](), [Java]() Tags: [code](), [java](), [modules](), [remote](), [remote-development](), [software-development]() ### AI overview The author describes lessons from building a remote software development team while working on a replacement for a rejected product system. Tightly coupled code and poorly isolated modules made independent work, onboarding remote developers, and integration difficult. ### Source excerpt Previously, I talked about the ill-fated rewrite of our core product. The 'second system', although better and faster than its predecessor, was rejected by the customer. But the story has a silver lining - one thing that we got right in the process that empowered us to grow and thrive: we built a highly productive remote development team. In this post, I'll share my experiences: how through trial and error (and with luck), we finally got the right formula and made it work for us. Part of the original system team was one of the best duct-tape developers I've ever worked with. We called him 'The Code Machine'. He didn't write clean code, but he wrote it fast as hell and made sure it worked. The original system, done with a gun to our heads, was a big, complex, monolith application and the boundaries between its modules were ill defined. Computer scientists refer to this type of code as tightly-coupled and the system is referred to as non-orthogonal. The 'second system' had a more grand vision and we needed to grow the team to build it right and on schedule. We hired another developer, a bright, young CS graduate to work on the system. One problem with the original system quickly became evident to me: because the code was tightly-coupled (the auto-generated UML class diagrams resembled a spider's cobweb), the new developer couldn't work independently: changing one part of the system indirectly impacted other parts. While they were not bickering, the two developers couldn't get out of each other's way and the progress was slow. Parallel to all this, the upper management decided to give 'remote software development' a try. Someone on the board recommended a company from Hyderabad, India and before I even knew it, I was interviewing a bunch of remote Java developers. The non-orthogonality problem was further magnified when the remote developer joined the team. Because the system was tightly-coupled, he was going to have to learn it all before he could become productive. S ## GNU Screen basics quick reference DevFeed: [GNU Screen basics quick reference]() Original publisher: [Read original article]() Author: Graham King Published: 2010-12-10T06:06:34Z Content type: tutorial Language: en Sources: [Graham King]() Topics: [screen](), [Command-line interface](), [ssh](), [remote-development]() Tags: [commands](), [remote](), [screen](), [sessions](), [split](), [ssh](), [strategy](), [terminal](), [unix]() ### AI overview A quick reference for GNU Screen covering installation, configuration, session attachment, essential keyboard commands, scrollback, and split windows. It focuses on using Screen to maintain multiple terminal sessions on remote machines over SSH. ### Source excerpt "Unlock the power of remote work with Screen: Your terminal multitasking companion!"