[iLearner]

Quote:

Originally Posted by Gamer_Z depends. When I had a server I let it restart at 02:00 am each day by pulling all updates in and automatically recompiling my mode. My workflow was: 1) Write code 2) test 3) commit & push 4) goto 1 Never had to touch the server, even crashdumps were automatically uploaded, which means I never had to ssh/rdp into the server and could do everything from my local pc (thanks to git). Without git: 1) Write code 2) test 3) recompile the mode yourself 4) connect to server console (be it ssh or rdp) 5) shutdown server 6) replace binaries 7) start server 8.a) if everything works goto 1, else: 8.b) crash 9) find and download crashdump 10) goto 1) You are probably using git anyway (or svn for the ones in the stone age) which means you are uploading your code twice, which sucks on slow connections. And that's why you want to automate the process. Great to see someone released a howto on this. Ofcourse my tip would be to make it a cronjob insteado f an php file that ssh's to a server, the server should do it itself. Git has commands to check if there are commits to be pulled. Would also be way more secure.. don't trust php.

Convincing, might give it a try.