News for hackers. Stuff that matters.
Re:SSH productivity tips by dwc on Tuesday August 16, 2011 @01:13PM (#2891986)
Have you considered doing something like pushing with git?
Re:SSH productivity tips by senko on Tuesday August 16, 2011 @01:34PM (#2892103)
This would suffer from the same problem.

But doing git push all is out of the question for me, because I'm rsyncing while developing, so I'd need to constantly commit and push tiny nonsensical commits to the server, and then do a massive rebase afterwards. In effect, it's more work and gains me nothing.

Re:SSH productivity tips by wfarr on Wednesday August 17, 2011 @12:24AM (#2894088)
I hope this is some sort of staging or testing server?

The idea of repeatedly writing code and rsyncing it up to a production server while adding new features/whatever seems incredibly error prone to me. And that's not even to touch on whether or not there's automated testing (in the form of unit/integration/whatever tests in the code).

Re:SSH productivity tips by senko on Wednesday August 17, 2011 @02:34AM (#2894369)
Yeah, it's a development server. I've got a cheap VPS (€4/mo with 512MB of memory) and I usually run the code I'm developing there.

My reasons: I don't have to pollute my laptop with various (sometimes mutually exclusive) servers - virtualenv &co are great, but can only go so far, and VMs are much harder on the battery; trivial for other people (colleagues, clients) to see WIP, even if my laptop is suspended.

Re:SSH productivity tips by philjackson on Wednesday August 17, 2011 @03:40AM (#2894489)
You should give Emacs and Tramp some consideration. Failing that, Fuse works well.
Re:SSH productivity tips by rauar on Wednesday August 17, 2011 @02:50AM (#2894402)
Which provider is that ?
Re:SSH productivity tips by senko on Wednesday August 17, 2011 @05:32PM (#2897036)
alvotech.de
Re:SSH productivity tips by rauar on Tuesday August 30, 2011 @04:52PM (#2943199)
Awesome. Will try it. Cheaper than linode. Curious how they perform.
Re:SSH productivity tips by tedunangst on Tuesday August 16, 2011 @01:25PM (#2892060)
Every push with git is going to create a new ssh connection. Using a shared connection is way faster.