Remote Dev Environments
Discussions revolve around the pros and cons of using remote, cloud-based, or virtualized development environments versus local setups, focusing on achieving consistency, matching production, and avoiding local configuration issues.
Activity Over Time
Top Contributors
Keywords
Sample Comments
You should try some cloud development environments - could give people a completely predictable environment.
True, but wouldn't you use Vagrant, Doccker or something similar to develop on? Can't speak for the OP's situation, but it seems a strange set-up that's all.
Some dev environments aren't local, and sometimes this is faster, especially if you have to document the changes for future updates that don't include your fancy tools.
That can happen when the dev environment is too complex / heavy to setup on a local machine.
I have a remote Linux server for my dev environment. This way it's one dev environment that I can access from any device.I am mostly using NeoVim now but in the past VSCode with the remote extension worked great too. It's totally platform agnostic (I can even work straight from my iPad). It's also a single instance that I have to manage instead of syncing or making changes in more than one place.With this setup I can still use docker containers or VM's to make it easy t
Yea it can be picking your own poison in some respects. My preferred workflow is something like spinning up a dedicated dev VM within your provider, install a standard image, then use a local text editor that's saving files over ssh or sftp.I have found virtually no one has problems with "well I can't get this to run on my machine and here are the n undocumented quirks". Everyone is using a homogeneous environment with local IDE help.This is in many respects similar to
I've used something like this in the past when working with tools that are difficult to host locally.Why setup your codebase and all the dependencies to run locally on a laptop when you can just spin up an instance on a server that matches your production environment and remote into it to work?
It's common to have your remote dev environment on a remote VM.
Why do people consistently try to run dev tools on their local OS when there are plenty of easy and cheap alternatives to accomplish more stable, reliable and reproducible environment?Just get a $5/mo cloud instance and run your stuff as same OS as production and let other people check your environment even while your machine is turned off and continue working on another machine without duplicating the environment.If you still want it locally, use VMware fusion which became free for p
I still don't see the necessity... Develop locally, test remotely.