I've got a production server I'm managing right now, but it's becoming incredibly inefficient to either:
- SSH into the remote server, and develop server-side
- Develop on my local machine and transfer changes to remote server
A possible remedy that came to mind was keeping a git repo that mirrored the filesystem of the remote-server (so the server's /var/www/html/ would be REPO/var/www/html), and then on push, having a git hook hardlink all of the files to their appropriate directories. Everything I'm currently pushing is just configs(e.g Nginx.conf)/interpreted files (e.g HTML/JS), so I don't see any issues popping up there. Even for compiled items, it seems to be as simple as using the same CPU architecture, during building, and then relinking server-side.
Am I missing something? I see only benefits here.