boob00 Posted March 26, 2015 Share Posted March 26, 2015 Hello everyone, I have recently acquired a website (www.example.net). Instead of paying for a third party to host it, I want to do it myself. The problem is, I am not to sure of how to configure apache for this. I have watched videos and looked around with little luck. What I am looking for is this, someone goes to example.net in their browser and gets to my site hosted on my server. Any help is beyond appreciated. Thanks! -boob00 Quote Link to comment Share on other sites More sharing options...
cooper Posted March 26, 2015 Share Posted March 26, 2015 Um... So what did you get? The domain? The site contents? The VPS that contains everything? A combination of these 3? Unless I'm mistaken, hosting can be had for as little as $50 a year. Are you really, really sure you wouldn't want to fork over a few bucks and let it be someone else's problem? Quote Link to comment Share on other sites More sharing options...
boob00 Posted March 26, 2015 Author Share Posted March 26, 2015 I got the domain, and I wrote the sites contents. -boob00 Quote Link to comment Share on other sites More sharing options...
mreidiv Posted March 27, 2015 Share Posted March 27, 2015 (edited) I got the domain, and I wrote the sites contents. -boob00 I have hosted several sites from my home and it was easy to set up but a pain to keep up with. First you have to have a static ip or at least a DNS service pointing to you router, some routers will only allow you to use the ones that are in your router all ready; then you have to forward the proper ports on your router ie 443 80 22 25 what ever you need and is safe. But before you do all of that you need to make sure that you have the server set up and secured correctly. I have moved all my sites to hosted becaus it is easier than continiously backing up my servers and keeping up with the security on them, plust the general site maintnence. Edited March 27, 2015 by mreidiv Quote Link to comment Share on other sites More sharing options...
cooper Posted March 28, 2015 Share Posted March 28, 2015 Take your own hourly wage. Divide 50 by that number. If you spend more than that amount of time in a year on keeping the box going, paying for hosting will be cheaper. If you went with a Windows machine to host the service, there will be the monthly patch tuesday at least, which on its own should account for 15 minutes of time spent on each. That's 3 hours per year. Add the odd service that acts up every so often or otherwise needs its own set of updates... it all adds up. I wouldn't be at all surprised when the math comes out at you needing to spend at least 1 hour per month on keeping the system going. Which would mean that if your hourly wage is over $4.20 your time is better spent working and paying someone else for the hosting. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.