Customize Apache Configuration
This workflow shows you how to add custom configuration to SUSE Manager} components, specifically the Apache HTTP server, within a containerized environment. It ensures that your custom configurations are stored in a persisted volume and are not overwritten during image updates.
1. Use case
This workflow is beneficial when:
-
You need to overwrite or extend the default Apache configuration.
-
You need to ensure that configuration changes persist after a container image update.
-
You want to add specific tuning configurations to the server.
2. Outcome
After completing this workflow, your custom Apache configuration will be active and will persist through future updates or restarts of the SUSE Manager} containers.
3. Preparation
Before you start, you should have:
-
Root access to the SUSE Manager Server host.
-
Knowledge of the specific Apache directives you wish to apply.
4. Step-by-step workflow instructions
|
You should only add new configuration files, and not modify the existing configuration files provided by the image. |
Open a terminal on your SUSE Manager Server.
Access the server container shell by running the following command:
mgrctl termNavigate to the configuration directory. You must create your new configuration file in the path
/etc/apache2/conf.d, as this folder is persisted.Create your new configuration file (for example,
custom_tuning.conf) and add your required Apache directives.Once you have saved your file, exit the container with xommand:
exitRestart the SUSE Manager services to apply the changes:
mgradm restart
5. Related topics
-
For more information on general server setup, see Installing SUSE Manager Using RAW Image.