3 ms·
Some examples that just come to my mind: - You need software/dependendencies/licences you don't have in your local machine. - You need to edit a config file (
by ghgr 12y ago
Some examples that just come to my mind:
- You need software/dependendencies/licences you don't have in your local machine.
- You need to edit a config file (/etc/hosts or whatever) in your server
- You are in a Windows computer (that's not yours) and you need to make a quick change in your Ubuntu development server.
- You need to edit some files when deploying (databases are no longer in localhost, /home/myname/ is /home/servername/, etc.)
- You launched a large script in your server and need to (view or parse logs | edit the code and re-launch it | check why it didn't work)
- etc.
- joshka 12y agosoftware deps - this is a possible fair point. I've always managed to solve this by bringing the deps local though as a general sanity rule. config - why not source control it? quick change - why would you do a quick change differently to a non-quick change? edit while deploying - why wouldn't you script / source control this for repeatability / maintainability? log parsing - it sounds like you've got an edit, verify loop going on. Why wouldn't you want to formalize this so that you can see which changes align with which results?