3 ms·
I don't edit code on servers either, but I frequently need to debug systems, or do experiments or develop in containers set up for that purpose. As such it's no
by vidarh 6y ago
I don't edit code on servers either, but I frequently need to debug systems, or do experiments or develop in containers set up for that purpose. As such it's not unusual for me to work with dozens of different environments in the course of even a week.
It's not just about having my editor available, but being able to trivially easily pull in the basic tools to do what I want, and that is especially important during emergencies, but it's also about convenience in other situations.
It sounds like you're lucky enough to deal with very simple environments. That's great. I'd still argue the cost in time of committing your config is so low that it'd be worth it. It takes pretty much one reinstall before it's paid for itself, or one instance of being somewhere without your usual environment.
Or one instance of doing something silly to a config and forgetting what you changed.
The nice thing about it is that it can start extremely light-weight - just literally a "git init" and .gitignore everything, and then gradually force add and commit.