Mailinglist Archive: opensuse (3729 mails)
| < Previous | Next > |
Re: [SLE] Running a webserver from a home machine...how?
- From: Derek Fountain <derekfountain@xxxxxxxxxxx>
- Date: Sun, 8 Jun 2003 13:29:18 +0800
- Message-id: <200306081329.18298.derekfountain@xxxxxxxxxxx>
On Sunday 08 June 2003 11:47, Tom Nielsen wrote:
> OK, I'm thinking it might be kind of cool (or keen to you EU folks) to
> run my own website from home. I don't know what I would do with it yet,
> but not the typical "here's my kids, here's my dog, here's our family
> reunion in Death Valley, blah...blah...blah". I might start up a local
> Land Rover club in my area and might choose to host it.
>
> So, with that being said:
> 1) How should I do this?
> 2) What server app should I use?
> 3) What is the downside to doing this? (I don't think I'll get 500 hits
> a day).
> 4) Will this have any effect on my system on a day to day basis?
> 5) I'm running a static, private IP on my machine from behind a
> firewall. Problem?
>
> Basically, I have a SMC cable router/firewall that I know how to setup.
> I have a static IP from my cable company. I have a pretty good system
> (processor, motherboard, memory, etc...).
>
> Feel free to start throwing out ideas. Also, is there a really simple
> way for me to do this right away? Like toss up something and see if
> someone can see it?
SuSE has a web server out-of-the-box for all versions since heck knows when.
Install the apache package and ensure it's set to start at boot time. As long
as your firewall port-forwards on port 80 it should just work (TM).
The downside is security. Once you have an entry point into your box from the
outside world, especially with a static IP address, you need to understand
exactly what that entry point allows and what abuse it might get put to. In
other words, you need to read up on Apache and ensure the config is set as
you need it. Don't just assume SuSE have set up a secure config which meets
your needs.
If you just want to serve static pages and photos, make sure you don't allow
PHP, mod_perl or any other of the other abusable things to be accessed from
the outside world.
Other than security, there's no significant downside really. The loading the
server puts on your box at 500 hits a day will get lost in the noise.
One other thing to consider is that you'll be running a service and if it's
any good people will start to depend on it. Once you reach that point you
have a responsibility to keep it going!
--
"...our desktop is falling behind stability-wise and feature wise to KDE
...when I went to Mexico in December to the facility where we launched gnome,
they had all switched to KDE3." - Miguel de Icaza, March 2003
> OK, I'm thinking it might be kind of cool (or keen to you EU folks) to
> run my own website from home. I don't know what I would do with it yet,
> but not the typical "here's my kids, here's my dog, here's our family
> reunion in Death Valley, blah...blah...blah". I might start up a local
> Land Rover club in my area and might choose to host it.
>
> So, with that being said:
> 1) How should I do this?
> 2) What server app should I use?
> 3) What is the downside to doing this? (I don't think I'll get 500 hits
> a day).
> 4) Will this have any effect on my system on a day to day basis?
> 5) I'm running a static, private IP on my machine from behind a
> firewall. Problem?
>
> Basically, I have a SMC cable router/firewall that I know how to setup.
> I have a static IP from my cable company. I have a pretty good system
> (processor, motherboard, memory, etc...).
>
> Feel free to start throwing out ideas. Also, is there a really simple
> way for me to do this right away? Like toss up something and see if
> someone can see it?
SuSE has a web server out-of-the-box for all versions since heck knows when.
Install the apache package and ensure it's set to start at boot time. As long
as your firewall port-forwards on port 80 it should just work (TM).
The downside is security. Once you have an entry point into your box from the
outside world, especially with a static IP address, you need to understand
exactly what that entry point allows and what abuse it might get put to. In
other words, you need to read up on Apache and ensure the config is set as
you need it. Don't just assume SuSE have set up a secure config which meets
your needs.
If you just want to serve static pages and photos, make sure you don't allow
PHP, mod_perl or any other of the other abusable things to be accessed from
the outside world.
Other than security, there's no significant downside really. The loading the
server puts on your box at 500 hits a day will get lost in the noise.
One other thing to consider is that you'll be running a service and if it's
any good people will start to depend on it. Once you reach that point you
have a responsibility to keep it going!
--
"...our desktop is falling behind stability-wise and feature wise to KDE
...when I went to Mexico in December to the facility where we launched gnome,
they had all switched to KDE3." - Miguel de Icaza, March 2003
| < Previous | Next > |