3 ms·
If you're editing files live on the server, you're doing it wrong. This argument ("Oh I use <insert console based editor> because I can use it on my laptop or
by stephenr 12y ago
If you're editing files live on the server, you're doing it wrong.
This argument ("Oh I use <insert console based editor> because I can use it on my laptop or via SSH on the server") is fucking stupid.
If you can learn how to use fucking vim or emacs, you can learn how to use configuration management - either through a "full blown" tool like puppet/chef/ansible/etc or through config packages (if you're on debian) or even through plain old shell scripts.
- pas 12y agoYes, yes, conf. mgmt. Yes, yes. Except when it's not really your call. And you have to poke around files so far down behind God's back through a shared desktop Enterprise VPN IE-only plugin-fest, that you don't even know which way is 127.0.0.1, then you're happy that you have vim on Dear Client's pointlessly supported RHEL boxes by default. And othertimes, when you want to debug something that only happens on a live/production server. Editing files on the server live is - in itself - not right or wrong. Doing it as a regular workflow is what's bad.
- AnimalMuppet 12y agoThat's a long way from original claim that "the vi/vim editing model is just superior to any other out there", though. "You may need it in some crippled environments, so it's handy to know" is a considerably weaker claim...
- cauterized 12y agoYou 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.