Apache httpd: Difference between revisions
from HTYP, the free directory anyone can edit if they can prove to me that they're not a spambot
module commands |
m →Official: old URL was for all Apache projects |
||
| (7 intermediate revisions by the same user not shown) | |||
| Line 13: | Line 13: | ||
* [[/mod_rewrite]] | * [[/mod_rewrite]] | ||
* [[/SSL]]: configuring Apache to serve [[https]] ([[secure sockets layer|SSL]]) | * [[/SSL]]: configuring Apache to serve [[https]] ([[secure sockets layer|SSL]]) | ||
* [[/variables]]: the <code>${varname}</code> syntax in Apache's config files | |||
===Related Pages=== | ===Related Pages=== | ||
* [[Apache and PHP]] | * [[Apache and PHP]] | ||
===useful commands=== | ===useful commands=== | ||
* <code>[[apachectl]]</code> | |||
** <code>apachectl configtest</code> tests the current configuration without trying to load it (which could result in Apache not running), and gives diagnostic information | |||
* <code>[[a2enmod]] {{arg|module_name}}</code> enables a module | * <code>[[a2enmod]] {{arg|module_name}}</code> enables a module | ||
* <code>[[a2dismod]] {{arg|module_name}}</code> disables a module | * <code>[[a2dismod]] {{arg|module_name}}</code> disables a module | ||
* <code>[[apache2_invoke]]: just noticed this in an update, not sure what it does (something like a2enmod?)</code> | |||
Enabling a module is ''usually'' just a matter of making links from the module's configuration files (sometimes there is more than one file) in <code>/mods-available</code> and putting them in <code>/mods-enabled</code>, but this is a safe and quick way to make sure that all the necessary files are linked. | Enabling a module is ''usually'' just a matter of making links from the module's configuration files (sometimes there is more than one file) in <code>/mods-available</code> and putting them in <code>/mods-enabled</code>, but this is a safe and quick way to make sure that all the necessary files are linked. | ||
| Line 24: | Line 29: | ||
<syntaxhighlight lang=bash>find . -name "*.log" | xargs tail -f</syntaxhighlight> | <syntaxhighlight lang=bash>find . -name "*.log" | xargs tail -f</syntaxhighlight> | ||
Note that if you are using [[Virtualmin]] to configure Apache, logfiles for the domains will probably be in <code>/var/log/virtualmin</code>. | Note that if you are using [[Virtualmin]] to configure Apache, logfiles for the domains will probably be in <code>/var/log/virtualmin</code>. | ||
==Links== | ==Links== | ||
===Official=== | ===Official=== | ||
* [http://httpd.apache.org | * [http://httpd.apache.org home page] | ||
** [https://cwiki.apache.org/confluence/display/HTTPD/ wiki] | |||
Latest revision as of 15:18, 1 April 2022
<hide> page type::article thing type::software architecture::server purpose::web server license::open source </hide>
About
This page is about the Apache web server software.
Subpages
- /.htaccess
- /mod_rewrite
- /SSL: configuring Apache to serve https (SSL)
- /variables: the
${varname}syntax in Apache's config files
Related Pages
useful commands
apachectlapachectl configtesttests the current configuration without trying to load it (which could result in Apache not running), and gives diagnostic information
a2enmod <module_name>enables a modulea2dismod <module_name>disables a moduleapache2_invoke: just noticed this in an update, not sure what it does (something like a2enmod?)
Enabling a module is usually just a matter of making links from the module's configuration files (sometimes there is more than one file) in /mods-available and putting them in /mods-enabled, but this is a safe and quick way to make sure that all the necessary files are linked.
To see all accesses to your Apache server in more-or-less real-time, run the following from your Apache logfile directory:
find . -name "*.log" | xargs tail -f
Note that if you are using Virtualmin to configure Apache, logfiles for the domains will probably be in /var/log/virtualmin.
