hosting a site on an in house apache server
 

hi guys,

just bought a domain at a hosting company...i want to experiment with apache and get the site working on my in house centos 7 server.

i google host web site apache
and a lot of results came up with apache virtual server and from what i understand this is used if you want to host multiple sites on one ip address...i have never setup apache before and am looking for clear cut advice to get a single web site viewable on a single server...my server...has anybody got a good instruction tutorial or any advice...would really appreciate it...

this looks like a good start,though it doesnt explain where the domain comes into play

http://www.liquidweb.com/kb/how-to-i...e-on-centos-7/

CentOS is a close relative of RHEL. Red Hat provides basic user to advanced admin documentation and therefore centos.org does to. I would suggest you put your server in a DMZ (or use virtualization?) and use the documentation (plus the one Apache provides) to first set up your single IP single web site and then expand to running multiple vhosts. The link you point to only tells you how to install Apache which isn't what you need. If you want generic HOWTO's best stay with common resources like those found on Howtoforge or cyberciti.biz.

hi unSpawn,

my server is in a center and sits on a vlan...so i have no control of the networking aspects of my server...though there is an admin i can get to do things for me. i have a centos server with 3 virtual machines running on virtualbox...am i better off learning to setup things within the vm of centos on the centos box? what are the benefits?

thanks for the reply

That's good to know.


Yes, in my opinion you would be better off. First of all you can create a template by creating a CentOS "minimal" install and populating it with the basic tools and configuration you need. Then you only have to copy the template and have a server ready in no time. You can take snapshots of a VM at any point in time. That way you can quickly restore if what you did last didn't work as planned. You can completely fsck up any VM and still be able to access it via the console (something you don't necessarily want to do with Production machines you don't have OOB access to ;-p). You can create your own isolated vlan, add system resources, IP addresses etc, etc all without any help from grumpy admins or even more grumpy data centre people ;-p And once you've settled for one configuration you can use it as template for the Production machine and Staging area to test things before rolling it out to Production.

hey unSpawn,

you said "That's good to know."...from your point of view? lol

is it worth learning this stuff...or should i be looking at other apache products? or is it easy to learn to use something else once you have the general idea of how things work...sorry...i feel very lost in the linux maze at times...im only trying to further my knowledge in the hope of being useful in the near future...thanks again

Yeah as it doesn't really add to the question at this point ;-p


If you'll be configuring, using, auditing, securing any web services you would like a rudimentary understanding of things so that's a yes from me.


Sorry but having it easy only fosters thinking about things the easy way. Using XAMPP in Production environments, new Linux users getting web-based control panels from their providers, not reading documentation, not controlling access, not heeding any warnings, not updating, etc, etc... Being in the position to see what the results are here and elsewhere I wish people focused on what matters: doing things the *NIX way. Yes, that is difficult at first but like all learning it takes preparation, practice and perseverance. Once you get the basic concepts right things will be easier. Did you start with some basic user documentation?

i installed apache last night...i have purchased a domain name and want to get apache displaying my study notes on a basic web site...but no havent found a good apache tutorial to do this...maybe i will purchase a book on apache. thanks again

You're rehashing. And (again) you're not reading well. That behaviour may well become a source of irritation in the future should you not change. I already told you where to look for nfo. I'll help you along with a list but please make an effort.

http://rute.2038bug.com/index.html.gz
http://lnag.sourceforge.net/download.html
https://access.redhat.com/articles/1189123
https://access.redhat.com/documentat...ide/index.html
https://access.redhat.com/documentat...ide/index.html
http://www.linuxhomenetworking.com/
http://httpd.apache.org/docs/2.4/ (the Users' Guide section) -> http://httpd.apache.org/docs/2.4/getting-started.html
https://access.redhat.com/documentat...b_Servers.html
https://wiki.centos.org/TipsAndTricks/ApacheVhostDir

A domain name will do little to no good if you don't get public IP numbers.

And now that the public IPv4 numbers have run out, you are limited to those your ISP can give out, or those your vlan provider can give out...

Now if you are using IPv6 and your vlan supports it.. and your domain servers support it, then you should be good to go.

One thing that help in populating your web server is to keep all of the files in a code management system (such as git). Thus when you want to restore/recover from accidents it becomes easy. I didn't, and things got rather complicated trying to extract only parts of backups.

thanks guys...yes will do unSpawn...sorry

Don't be sorry, be reading already! ;-p