The Apache HTTP server is a mighty beast that powers the majority of websites. It has developed into a posh server that slices, dices, dances, and sings. It powers vast internet hosting centers, and it is usually splendid for operating small private websites.
The trick with Apache is realizing which configurations you need because it has loads to select from. We’ll start with organising a single site, after which in part 2 set up SSL, which is vitally important, and we’ll study a bit in regards to the .htaccess file. Yes, .htaccess, that wonderful file that allows us to make per-directory configurations, however which uses such a contorted syntax it reduces essentially the most stoic server admin to tears and whimpers. The good news is you never want to use .htaccess you probably have entry to your Apache configuration files. However when you don’t, for instance on shared internet hosting, you need .htaccess.
On this series we’ll tackle Debian/Ubuntu/Mint and Fedora/CentOS/Purple Hat separately, because the varied Linux households are all particular flowers that really feel they must set up the Apache configuration files in their own distinctive ways.
On Debian/and so on. install Apache with this command:
This installs Apache, utilities, configuration information, and different gadgets you possibly can see with apt-cache show apache2. Debian/Ubuntu begin Apache routinely after installation. Point your net browser to http://localhost to verify that it’s working; you need to see the default index page (Figure 1).
Where is Everything
Configuring Apache seems complicated at first, however while you research the configuration files you see a nice modular scheme that makes it straightforward to handle your configurations. The configuration files are in /etc/apache2. Spend some time finding out your configuration file construction and studying the default configuration recordsdata. It’s best to have these information and directories:
The principle server configuration file is /etc/apache2/apache2.conf. You won’t spend much time enhancing this file as it ships with a complete configuration, and it calls different configuration files for the bits you should customize. Look in here to see the placement of server configuration information, your HTTP user and group, included recordsdata, log file areas, and other international server configurations.
conf-obtainable accommodates further server configurations. Keep any extra international configurations in this listing, somewhat than including them to apache2.conf.
mods-accessible contains configurations for all put in modules.
websites-out there accommodates configurations for your virtual hosts. Even if you’re running solely a single site you’ll set it up in a virtual host configuration.
Not one of the configurations in these directories are active until they are symlinked to their respective *-enabled directories. You have to use Apache commands to arrange new sites accurately, which we’ll get to in the next part.
envvars accommodates Apache’s atmosphere variables.
magic has file MIME varieties, in order that Apache can quickly determine the file sort from its first few bytes.
ports configures the TCP ports that Apache listens to.
Single Site
The set up comes with a default site that’s configured in sites-obtainable/000.default.conf. You can modify and use this, but it’s higher to leave it alone because it’s a helpful testing software. Let’s be like real nerds and make our new site from scratch. First create its document root (which in this example is take a look at.com), インフラエンジニア 未経験 enter the new listing, then create and take a look at your pattern index page:
Feel free to copy this to your new check web page. It must be named index.html and go in your doc root:
Good day, welcome to test.com! It really works!
That’s all I have to say. If you don’t see this then it would not work.