3 ms·
You can host a non-production development environment on a remote server. That can help ensure it's as similar as possible to your production environment, as we
by cauterized 12y ago
You can host a non-production development environment on a remote server. That can help ensure it's as similar as possible to your production environment, as well as making it easier to move between locations / computers without having to sync your Dev environment.
Oh, and if you're editing system config files for systems administration tasks? That's on the server. As GP said, if you come from a sysadmin background, you're used to using a keyboard-only editor. And Vim sure beats ed.
- stephenr 12y agoConfiguration files should be modified/replaced by configuration management systems/tools - that was my whole point. You don't edit code live on the server (you commit it to vcs and have a deployment system, right?) so why would you edit config files live?
- cauterized 12y agoUntil a few years ago, almost nobody did things this way (the tools just weren't there); and even now, there are plenty of people who don't. It's too much overhead to deal with if you're spinning servers up and down only infrequently.
- stephenr 12y agoNo one cared about anything until we discovered/identified a better way to do said thing. If you're doing it infrequently this is even more of a reason to use a reproducible system, otherwise recreating the environment when the inevitable happens is even harder (you don't even have the benefit of repeated steps to aid you in the process) I know some of the existing tools are a massive overhead for small operations - that doesn't make the goal in general any less worthy.