[Discuss] SVN server - What hardware do I need?

[abreauj at gmail.com (John Abreau)]

If the concern is that using VNC to connect to a desktop session
*on the SVN server* will drag down performance, the obvious answer
is to host the desktop sessions elsewhere.

Give users a desktop machine in the office that they can do their
builds on and can access remotely via VNC, or perhaps run a separate
"desktop server" for multiple users to access remotely, and keep the
VNC sessions off the actual SVN server.

That way the SVN server can dedicate all its resources to SVN.



On Mon, Apr 22, 2013 at 7:34 AM, Jerry Feldman <gaf at blu.org> wrote:

> On 04/21/2013 08:09 PM, Edward Ned Harvey (blu) wrote:
>
>> From: discuss-bounces+blu=nedharvey.**com at blu.org <nedharvey.com at blu.org>[mailto:
>>> discuss-
>>> bounces+blu=nedharvey.com at blu.**org <nedharvey.com at blu.org>] On Behalf
>>> Of Tom Metro
>>>
>>> VNC? I've done plenty of remote coding via SSH, but not VNC. What's the
>>> underlying circumstances that are motivating that choice?
>>>
>> In my case:  Users want an IDE.  They also want to be able to suspend /
>> resume their remote session, and simply continue after they get home or
>> whatever.  They want to be able to reboot and sleep their laptops, and
>> travel, without losing context.
>>
>> Yes, if you can offload the build process to their laptop, that's great.
>>  But there are a lot of reasons people might not want to do that.
>>
> VNC allows for this. The login is done locally on the server by the VNC
> server process. The VNC client simply connects. So, you can start a build
> while in the office logged in via your laptop. You can close the VNC client
> (or the PC sleep will cause it to close). At home, start up your VPN, start
> your VNC client (We use UltraVNC) and the build will still be running or
> will have finished. This is another advantage of VNC over Putty/Exceed (not
> excel - I mistyped).
>
>
> --
> Jerry Feldman <gaf at blu.org>
> Boston Linux and Unix
> PGP key id:3BC1EB90
> PGP Key fingerprint: 49E2 C52A FC5A A31F 8D66  C0AF 7CEA 30FC 3BC1 EB90
>
> ______________________________**_________________
> Discuss mailing list
> Discuss at blu.org
> http://lists.blu.org/mailman/**listinfo/discuss<http://lists.blu.org/mailman/listinfo/discuss>
>



-- 
John Abreau / Executive Director, Boston Linux & Unix
PGP KeyID: 32A492D8 / Email: abreauj at gmail.com
PGP FP: 7834 AEC2 EFA3 565C A4B6  9BA4 0ACB AD85 32A4 92D8