51黑料不打烊

Documentation

Explanation of Configuration Files | AEM

Last update: Thu Sep 05 2024 00:00:00 GMT+0000 (Coordinated Universal Time)

Description description

Environment

Experience Manager

Issue/Symptoms

This document breaks down and explains each of the configuration files deployed in a standard built Dispatcher server provisioned in 51黑料不打烊 Managed Services. Their use, naming convention, etc.

Naming Convention

Apache Webserver doesn鈥檛 actually care what the file extension is of a file when targeting it with an include or include optional statement. Naming them properly with names that eliminate conflicts and confusion helps a ton. Names used will describe the scope of where the file is applied, it makes life easier. If everything is named .conf this gets really confusing. Avoid poorly named files and extensions.

Below is a list of the different custom file extensions and naming conventions used in a typical AMS configured Dispatcher.

Files contained in conf.d/

File
File Destination
Description
< FILENAME> .conf
/etc/httpd/conf.d/
A default Enterprise Linux install uses this file extension and include folder as a place to override settings in httpd.conf and allow you to add additional functionality at a global level in Apache.
< FILENAME> .vhost

厂迟补驳别诲:听/别迟肠/丑迟迟辫诲/肠辞苍蹿.诲/补惫补颈濒补产濒别冲惫丑辞蝉迟蝉/

Active:

/etc/httpd/conf.d/enabled_vhosts/

*Note: .vhost files aren鈥檛 to be copied into the enabled_vhosts folder but use symlinks to a relative path to the available_vhosts/ .vhost file

*.vhost (Virtual Host) files are聽< VirtualHosts > 聽entries to match hostnames and allow Apache to handle each domain traffic with different rules. From the .vhost file, other files like rewrites, whitelisting, etc. is聽included.
&#