You're right. There comes a time when you've learned all you can by hosting something on your own, and you're ready to stop worrying about the conditions of running a server out of a home network. I used to host my web and email at home, but I've since moved everything to a commercial host. Not because I don't have the ability to do it myself, but because it's just not worth it when I can pay a little money and have someone else provide all the hardware, bandwidth, backups, environment, and power requirements that someone like me who lives in an apartment can't. I get all the server administering practice I need at work--I don't need to build a 3rd rate network out of spare parts at home and risk pissing off my ISP.
Adam Melancon wrote: >Yes, but if cox is blocking port 80, how are you going to explain to >grandma to go to melancon.org:8080/gallery/ when they have a hard >enough time with melancon.org? > >Plus, I'd like to politely defend my own recent lack of DIY when it >comes to my webserver. >Melancon.org has been running as a test machine on my network at work >where I am/was the systems administrator for the vermilion parish >library. It was hosted on the test machine and I setup my own DNS >entries at www.granitecanyon.com. It served its purpose for the time >and allowed me to exeriment with things before I did them on the >actual production machines. At this library I have probably about 7 >linux servers, several linux desktops for staff and patrons, and two >windows servers. I've setup everything from linux terminals to >firewalls to webservers to squid caching servers and filters. It's >not that I don't want to tinker, its just that I just want to upload >the photos and forget about maintaining that machine for a while. >I just got a new job in Lafayette where I will be the systems >administrator for all 10 libraries in Lafayette parish, so my hands >will be full for now. > >Just figured I'd give some back story on why I was looking to host it. > >On 5/3/05, Joseph Fruchey <[EMAIL PROTECTED]> wrote: > > >>Okay, so how do I point my registrar to direct my domain name to the >>server at my house? >> >>On 5/3/05, michael dolan <[EMAIL PROTECTED]> wrote: >> >> >>>At the risk of being modded -1 repetitive, I totally agree. >>>I had never even heard of linux and had only owned my first computer for >>>about 3 months when I got into a conversation about running your own web >>>server. Someone said it couldn't be done from home with no budget, I >>>disagreed even though none of us had any idea what we were talking >>>about, and they challenged me to do it. I did it, became a geek, and >>>turned my apartment into a computer graveyard. It was like peeling an >>>onion, and every layer just made me more interested. From what is this >>>linux thing I hear about on the internet, to the philosophy of free >>>software, to actually learning (on my own) how internet protocols work >>>by making mistakes and actually making them function. When I started, I >>>didn't even know how to ask a question, and I am incredibly embarrassed >>>when I stumble across some of my old posts on linuxquestions.org, but I >>>did it and I loved it. >>>Michael >>> >>>Joey Kelly wrote: >>> >>> >>> >>>>Guys, >>>> >>>>Maybe it's just me, but when I got into this thing back early 2000, the >>>>thing >>>>to do if you were a self-respecting Linux geek was to set up your own >>>>web/mail/DNS/whatever server if you were rich enough to get a DSL line. I >>>>understand that several providers have taken it upon themselves to block >>>>outbound web and mail, but still, I see a lack of enthusiasm on this list >>>>and >>>>the nolug list about such things. >>>> >>>>Maybe everyone's just into using Linux as a desktop OS these days, and >>>>that's >>>>fine, but if any of you are thinking of doing any kind of administration or >>>>support for a living, I strongly suggest that you leverage the fact that you >>>>have at your disposal the best networking OS available, for free. You might >>>>not have access to Cisco gear --- I still don't, but that hasn't stopped me >>>> >>>> >>>>from learning at least something about practically every aspect of >>>>networking >>> >>> >>>>and computers. As a result of my inquisitiveness and tinkering, I quite >>>>often >>>>end up instructing Cisco- and other-certified techs a thing or two now and >>>>then. I don't claim to be much of an expert, you understand, but I've played >>>>with this stuff on a non-click-and-drool OS for so long, I've gotten to know >>>>my way around the networking model. >>>> >>>>^C >>>> >>>>On Monday May 2 2005 20:41, michael dolan spake: >>>> >>>> >>>> >>>> >>>>>It's actually been a few years since I've done it. I think it might be >>>>>time to do it again. I just played around with it anyway, and when the >>>>>Mb died in that computer I stopped.. I knew cox upped both down and >>>>>upload speed, but I had a brain freeze. Sorry, I had an exam today. >>>>>Michael >>>>> >>>>>Joey Kelly wrote: >>>>> >>>>> >>>>> >>>>> >>>>>>On Monday May 2 2005 17:24, michael dolan spake: >>>>>> >>>>>> >>>>>> >>>>>> >>>>>>>You can easily get around your ISP blocking port 80, but the upload >>>>>>>speeds will kill you on a cable connection. >>>>>>> >>>>>>> >>>>>>>------------------------------------------------------------------------ >>>>>>> >>>>>>>_______________________________________________ >>>>>>>General mailing list >>>>>>>[email protected] >>>>>>>http://brlug.net/mailman/listinfo/general_brlug.net >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>_______________________________________________ >>>General mailing list >>>[email protected] >>>http://brlug.net/mailman/listinfo/general_brlug.net >>> >>> >>> >>_______________________________________________ >>General mailing list >>[email protected] >>http://brlug.net/mailman/listinfo/general_brlug.net >> >> >> > > > >
