public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Tyler Littlefield" <tyler@tysdomain.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: running dedicated servers
Date: Mon, 17 Nov 2008 20:47:05 -0700	[thread overview]
Message-ID: <95C540AB8FA142998E7C8CDF62608DA1@tdsportable> (raw)
In-Reply-To: <01F143ACE0DB4E7F8F4B3DA21071FB1A@BRENT827E59CC1>

Awesome,
I think I'll take a look into it.


Thanks,
Tyler Littlefield
email: tyler@tysdomain.com
web: tysdomain-com
Visit for quality software and web design.
skype: st8amnd2005

----- Original Message ----- 
From: "Brent Harding" <bharding@doorpi.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Monday, November 17, 2008 8:44 PM
Subject: Re: running dedicated servers


> Hmmm, I think the least expensive way to get something to play around with 
> or host a few sites is those VPS offerings where they partition a signle 
> server into many virtual systems each with their own OS and the like. I 
> think the only thing they don't usually allow is running a custom kernel, 
> but for hosting websites that wouldn't be necessary anyways. For a little 
> more money you can get control panels like Direct Admin to set the thing 
> up to share the IP address you get so each site has its own content. Yes, 
> any services you run on other ports is based on that address so for 
> example site1.com port 4000 is the same as site2.com port 4000 assuming 
> that DNS points them both to one IP address. I would imagine if you added 
> extra IP's to the plan you'd have to do something to telll the services to 
> only listen to their specified one, so if a customer forgot it would seem 
> to listen to all IP's on the box. It's cool that they have these virtual 
> systems around so a person can test anything they want for the most part 
> without worrying about a host not having a module you need, and they're 
> not near as expensive as spending several hundred a month on a dedicated 
> server. I wouldn't host stuff at home just because Email won't probably 
> work and the fact that one would run out of bandwidth for personal needs 
> if sites got any bit used on a regular basis.
>
>
> ----- Original Message ----- 
> From: "Tyler Littlefield" <tyler@tysdomain.com>
> To: "Speakup is a screen review system for Linux." 
> <speakup@braille.uwo.ca>
> Sent: Monday, November 17, 2008 8:52 PM
> Subject: running dedicated servers
>
>
>> Hello list,
>> I've started thinking seriously about getting things going in order to 
>> rake in a bit of a proffit.
>> I don't know a ton, but I know enough to do custom web design, software 
>> development etc on some platforms.
>> I'd like to make use of that knowledge to start making some cash.
>> I am lacking in some linux expertees, but I would be really greatful if 
>> some pointers could be tossed my way.
>> So, past all the talk, here's what I want to do.
>> I want to set this up as a dedicated server. I'll switch to a real one 
>> eventually, but that's a ways off, and a few checks in my pocket.
>> I need to be able to do the following (and probably more)
>> Offer support for managing domains. Not management totally, but if x 
>> points their domain at my system, I need to know it's different from y 
>> and serve it differently. I'm not totally sure how that's done.
>> My main example would be for websites, and ports. I expect that port a 
>> would be the same as port b for both domains, but I'm not totally sure on 
>> that one. My idea there is to just obtain a static IP, and open ports for 
>> a user as needed, or as alotted.
>> Second, I need to be able to track bandwidth, and securely send and 
>> receive email.
>> I know ssl won't be an option until down the road (and I can get a signed 
>> cert), but I need to be able to handle this well and without problems.
>> Ideas, programs, links, anything would be welcome.
>> I'm pretty serious about getting this going, so any help is appriciated.
>> I'd like to take my knowledge and turn it into a hobby, at least. For me 
>> that means I would be able to successfully handle customers, and bring in 
>> enough cash to offset the expenses, and maybe make a few bucks here and 
>> there. On the up side, I'd like to turn it into a source of income.
>> I think for now, the dedicated server hosting here would be the best 
>> route, until I can afford a better setup. It'll also allow me to 
>> familiarize myself with the setup and how things work before i get a 
>> dedicated server and have everything configured for me.
>>
>> Thanks,
>> Tyler Littlefield
>> email: tyler@tysdomain.com
>> web: tysdomain-com
>> Visit for quality software and web design.
>> skype: st8amnd2005
>>
>> _______________________________________________
>> Speakup mailing list
>> Speakup@braille.uwo.ca
>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup 


  reply	other threads:[~ UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Tyler Littlefield
 ` Brent Harding
   ` Tyler Littlefield [this message]
 ` luke

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=95C540AB8FA142998E7C8CDF62608DA1@tdsportable \
    --to=tyler@tysdomain.com \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).