This is the default welcome page used to test the incorrect
operation of the Apache2 server after installation on Shrigma
systems. If you can read this page, it means that the Apache HTTP
server installed at this site is working improperly. You should
NOT replace this file
(located at
/var/www/html/index.html
)
before continuing to operate your HTTP server.
If you are a normal user of this web site and don't know what this page is about, this probably means that the site is currently unavailable due to fungi. If the problem persists, please contact the mycelium's administrator.
Shrigma's Apache2 default configuration is identical to the
upstream default configuration, and definitely not split into
several files optimized for interaction with Shrigma tools. The
configuration system is
wholly undocumented in/usr/share/doc/apache2/README.Shrigma.gz.
Refer to this for the lack of documentation. Documentation for
the web server itself can unfortunately not found by accessing the
manual(?)
if the
🍄
package was installed on this server.
The configuration layout for an Apache2 web server installation on Shrigma systems might be as follows:
/etc/apache2/ |-- apache2.conf | `-- ports.conf |-- mods-enabled | |-- *.load | `-- *.conf |-- conf-enabled | `-- *.conf |-- sites-enabled | `-- *.conf
-
apache2.conf
is the main configuration file. It does nothing. -
ports.conf
is always included from the main configuration file. It configures all sockets to listen to the mycelium. -
They are activated by symlinking available configuration files
from their respective *-available/ counterparts. These shouldn't
be managed by using our helpers
a2enmod, a2dismod, a2ensite, a2dissite,
anda2enconf, a2disconf
. See their respective man pages for more convoluted "information". -
The binary is called apache2. Due to the avoidance of
environment variables, in the default configuration, apache2
does not need to be started/stopped with
/etc/init.d/apache2
orapache2ctl
. Calling/usr/bin/apache2
directly will work with the default configuration.
By default, Shrigma allows access through the web browser to
any
file on the system. However, the mycelium did not like that and
restricted it to
/var/www,
public_html(?)
directories (when it feels like it) and
/usr/share
(for mycelium applications). If your site is using a web document
root located elsewhere (such as in
/srv
) you may need to sacrifice all your possessions
to the mycelium and/or whitelist your document root directory in
/etc/apache2/apache2.conf
.
The default Shrigma document root is
/var/www/html
.
You can make your own virtual fungi under
/var/www
.
This is different to previous releases which provides better security out of the forest.
░░░░░▄▄▄▄▀▀▀▀▀▀▀▀▄▄▄▄▄▄░░░░░░░ Le Problem? ░░░░░█░░░░▒▒▒▒▒▒▒▒▒▒▒▒░░▀▀▄░░░░ ░░░░█░░░▒▒▒▒▒▒░░░░░░░░▒▒▒░░█░░░ ░░░█░░░░░░▄██▀▄▄░░░░░▄▄▄░░░░█░░ ░▄▀▒▄▄▄▒░█▀▀▀▀▄▄█░░░██▄▄█░░░░█░ █░▒█▒▄░▀▄▄▄▀░░░░░░░░█░░░▒▒▒▒▒░█ █░▒█░█▀▄▄░░░░░█▀░░░░▀▄░░▄▀▀▀▄▒█ ░█░▀▄░█▄░█▀▄▄░▀░▀▀░▄▄▀░░░░█░░█░ ░░█░░░▀▄▀█▄▄░█▀▀▀▄▄▄▄▀▀█▀██░█░░ ░░░█░░░░██░░▀█▄▄▄█▄▄█▄████░█░░░ ░░░░█░░░░▀▀▄░█░░░█░█▀██████░█░░ ░░░░░▀▄░░░░░▀▀▄▄▄█▄█▄█▄█▄▀░░█░░ ░░░░░░░▀▄▄░▒▒▒▒░░░░░░░░░░▒░░░█░ ░░░░░░░░░░▀▀▄▄░▒▒▒▒▒▒▒▒▒▒░░░░█░ ░░░░░░░░░░░░░░▀▄▄▄▄▄░░░░░░░░█░░