file/print/web server

[Matthew Kuiken]

blkish wrote:
> agreed. best to seperate production and testing servers wherever
> possible. especially if the production server contains 'critical' data.
>
> (when does a production server become a testing server.. and did you
> ever mean for that to happen etc)
>   
I just happened to have the old computer lying around, so I decided to 
see if I could resurrect it.  As far as using it for a backup server, 
after having dropped my laptop once, and the USB drive that I am using 
for a backup another time, I realized that in order to be safe that my 
personal data would not be lost, I should back it up to a fixed 
machine.  I just happened to resurrect the old machine right about the 
time that I decided to make better backups...
> an old 486 would do as a basic webserver even. as mentioned above you
> can put this outside your firewall also if desired, though just as easy
> to foward ports 22 (ssh) 80 (http) and 443 (https) to the new web
> serving machine.
>
> good luck :)
>   
I thought of the application for a web server on a whim.  It is an idea 
mainly for community collaboration in a very small community.  I haven't 
entirely decided I even want to propose it yet.  I just thought it was a 
neat idea to use for this old machine that I happened to resurrect.  I 
only recently realized that doing so would put my personal backup data 
onto a web facing machine that would be subject to the automated attacks 
the web has to offer.

It's beginning to sound like a bad idea.  I will probably just stick 
with using it for file/print server, and drop the web idea entirely.  
OTOH, my friend has an old machine that he never uses anymore, maybe I 
can get him to donate to the cause...

-Matt