[nmglug] WWW service provider

[Aaron Birenboim]

On 03/01/2011 10:48 AM, David Borton wrote:
> I agree.  Don't encourage GoDaddy.  Brownrice is great... very
> knowledgeable and besides they are local.
>
> If you need to shave the cost down to $7 / month, you can try KnownHost
> @  http://www.knownhost.com/shared-hosting.html.  I am using them for
> two sites and they do cover the basics with fast support.  No problems
> so far.
>
> It sounds like all Aaron wants is storage, so maybe dropbox would work.

Will look at KnownHost.  How much does storage on dropbox cost?

I'm thinking of a hybrid solution.
I think Google/Google-apps will let me manage e-mail forwards,
DNS records, basic static WWW page...

So I could just pay for a service with decent storage policy/support.

If we want to do any fancy Internet services, we could link to
a sub-domain serviced by a computer in the office.
It will be good to have a "root" presence off-site since we
have 85-90% uptime at best at the office.
(Gotta love Comcast, and frequent power outages)

                 aaron

> On 03/01/2011 08:09 AM, michael w wrote:
>> Brownrice was my local choice in NM out of Taos.  Personal attention
>> and professional service.  No shell access.
>> http://hosting.brownrice.com/
>>
>> Dreamhost is widely used and also offers an included deliberate
>> "backup" account setup to use rsync/sftp/etc to manage backups at 50GB
>> +.  Their services are comparably slow, but cheap.
>>
>> Godaddy should be taken to court for wasting hours of everyone's time
>> who has ever touched their website.  Please, do not encourage them.
>>
>> --mikey in Sea.
>>
>> On Mon, Feb 28, 2011 at 8:53 PM, Andres Paglayan<andres at paglayan.com>  wrote:
>>> On Mon, 2011-02-28 at 15:51 -0700, Aaron Birenboim wrote:
>>>
>>> I need to find a new Internet hosting provider.
>>>
>>> read below only if the provider you are abandoning is not dreamhost,
>>>
>>> All I used them for was:
>>>
>>>    * e-mail forwarding
>>>         - forward the vanity domain addresses to appropriate
>>>                yahoo/google mail accounts
>>>    * DNS management
>>>        - use their DNS server to point some sub-domains
>>>           to the static IPs at our office
>>>    * WWW/storage?
>>>          We really did not use WWW,
>>>          We just used the WWW storage area
>>>          for on-line backups.
>>>
>>>
>>> We use dreamhost exactly with the features you mentioned above,
>>> for some domains we use their email servers,
>>> others transparently forward to google (never tried yahoo)
>>>
>>> we run a bunch of heavy web apps on servers colocated in Albuquerque (Prism)
>>> and we use DH DNS to redirect all http related,
>>>
>>> For a another couple of domains,
>>> we just manage DNS from godaddy,
>>> to direct requests to our servers without using DH email srvs nor their DNS
>>>
>>> although DH offers unlimited all
>>> I remember that when running a memory intense app,
>>> it will be just killed if the memory of its process goes over a little
>>> threshold,
>>>
>>> with storage that doesn't seem to be a problem,
>>> you can copy your keys and do rsync to any folder on your /home
>>> it won't be seen unless on a http path, or you can put your own .httpaccess
>>> file,
>>>
>>> you can even install git locally and run your repos there,
>>> (you can really install whatever you want via ssh on your own user account)
>>>
>>> although for hosting code I'd recommend http://github.com
>>> it is our only place for code, we pay a private plan and is totally worth
>>> it,
>>>
>>>
>>>
>>>
>>> Both godaddy and 1and1 offer WWW hosting plans
>>> with 150-250 GB storage for around $10/month.
>>> ******************************
>>> *******************
>>> *** Anybody know if we will be able to get away
>>> *** using them as detailed above?nigricans
>>> **********************************************
>>> i.e.  We really didn't use the WWW hosting,
>>>        but we pushed some cyphertext up there for backup.
>>>
>>> Both claim some sort of ssh access.
>>> It is my hope that we can find a way to run
>>> something like rsync over that ssh,
>>> and perhaps make our cyphertext non-readable
>>> to the WWW server.  Worst case, put
>>> it in a folder that is shut off using
>>>    .htaccess?
>>>
>>> The off-line storage will be just for a few critical things,
>>> like source code repositories.
>>> I think we can keep it to about 10-40GB (depending on pruning),
>>> with very little storage update bandwidth.
>>>
>>>    Thanks for any advice,
>>>
>>>           aaron
>>> _______________________________________________
>>> nmglug mailing list
>>> nmglug at lists.nmglug.org
>>> http://lists.nmglug.org/listinfo.cgi/nmglug-nmglug.org
>>>
>>>
>>> _______________________________________________
>>> nmglug mailing list
>>> nmglug at lists.nmglug.org
>>> http://lists.nmglug.org/listinfo.cgi/nmglug-nmglug.org
>>>
>>>
>> _______________________________________________
>> nmglug mailing list
>> nmglug at lists.nmglug.org
>> http://lists.nmglug.org/listinfo.cgi/nmglug-nmglug.org
>>
> _______________________________________________
> nmglug mailing list
> nmglug at lists.nmglug.org
> http://lists.nmglug.org/listinfo.cgi/nmglug-nmglug.org