5 ms·

[{[[{[{[{[{}]}}}]}]]}] Spot the typo! If you think this is stupid because surely everyone uses an editor with automatic scope highlighting etc, I don't think

• heinrich5991 10y ago
  vim works via SSH. :)
• michaelmior 10y ago
  If you work on a team with someone who writes config files like that, I think you've got bigger problems.
• vidarh 10y ago
  If you are remotely editing config files, then that is the problem.
  • vertex-four 10y ago
    In practice, not everybody is managing 10+ identical servers, and manual config + backups works well enough.
    • tclancy 10y ago
      I have dozens of small web projects. Part of my project boilerplate is a Fabric file that runs tests and deploys. There's no reason to hand-edit a file on the server unless something is already on fire. And even then . . .
      • vertex-four 10y ago
        I assume that you already have Apache, your firewall, etc etc set up on the server though? You likely manage OS package updates somehow outside of Fabric? A fair bit of my stuff co-exists with other things on the same server, so a per-project deployment system couldn't manage everything without occasional conflicts.
    • vidarh 10y ago
      Personally I deploy everything in Docker containers now, so I test a static image and push a bit for bit identical image. (EDIT: Even for individual / one-off setups, yes) But even if you want to do "manual" changes without Docker, or without a configuration management solution like Puppet etc., I'd do them locally in a git repo or similar and either git pull'ing it or rsyncing it over. Both because it'd mean flexibility in terms of tooling, but also because it makes it easy to actually test it first, or at the very least e.g. syntax check them.