Complete.Org: Mailing Lists: Archives: gopher: April 2008:
[gopher] Re: Gopher server on shared host

[gopher] Re: Gopher server on shared host

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: gopher@xxxxxxxxxxxx
Subject: [gopher] Re: Gopher server on shared host
From: Brandon Poder <xythonix@xxxxxxxxx>
Date: Thu, 03 Apr 2008 11:29:39 -0500
Reply-to: gopher@xxxxxxxxxxxx

Cameron Kaiser wrote:
>> Any recommendations for a Gopher server to run in a shared Linux hosting
>> environment?
>> We're on DreamHost PS (, so can run processes,
>> but do not have root access. I've looked at some of the gopher servers on
>> offer and a recommendation would be helpful. Thanks!
> The primary problem you will have is running a process on port 70. If your
> package allows you to bind port numbers that low through some sort of
> trusted method, and you have your own IP, there should be no problem.
> If you cannot bind port 70, you can still run a server on a high port
> number such as 7070. How you would do this depends on the server package
> you use. The primary issue there is that Mozilla is hardcoded to only use
> port 70, part of the thing that OverbiteFF seeks to change (speaking of
> which, there will be a new OverbiteFF release later tonight -- more shortly).
I find it odd that you do not have root access on a shared host.  I 
currently run two separate VPS servers that are remotely hosted via Xen 
that both allow full root access and all major ports and the ability for 
multiple ip's for an extra dollar per month.  I use VPS Land and NDC 
Host both allowing full control over your VPS.  The prices are 
reasonable I actually prefer NDC host over VPS Land but I required two 
separate servers for Python network development that would allow for 
rapid data transmission between the two servers.


[Prev in Thread] Current Thread [Next in Thread]