Installing apache on opensuse

I use rsync as it can be reliably restarted if required or run again to double check all files were copied in full. Your DVD label in the media directory may differ from the example here. As we have not put the install files there we need to setup a virtual directory to point the webserver to this using an alias.

To set this up we first must understand a little about the configuration files in openSUSE for Apache. Some Linux distributions use just this file with all configurations in the one file. Essentially the httpd.

As we can see from the graphic, on openSUSE, the apache configuration is made from many files not just the httpd. The conf. It has to be.

Of course you will need to use a test editor. The file will look like this and I wil explain the contents. The Indexes option allows for directories without index. Again, the best way to do this is to create a PHP file and have Apache serve it and be able to display it. Again, save the changes and close the editor.

This makes it a basic thing to learn. But every Linux distribution has a way of working with them. This is thanks to the stability and reputation that a distribution that knows how to do things enjoys. But the result is the same.

Refer to Section Note that configuration files for optional modules reside in the directory conf. Contains configuration directives for the different MPMs see Section Properly test your Web server when making changes here.

Do not put other configuration files in this directory. Your virtual host configuration should be located here. The directory contains template files for virtual hosts with and without SSL. Every file in this directory ending with. Configuring Apache manually involves editing plain text configuration files as user root.

The term virtual host refers to Apache's ability to serve multiple universal resource identifiers URIs from the same physical machine. This means that several domains, such as www. It is common practice to use virtual hosts to save administrative effort only a single Web server needs to be maintained and hardware expenses each domain does not require a dedicated server.

Virtual hosts can be name based, IP based, or port based. To list all existing virtual hosts, use the command apache2ctl -S. This outputs a list showing the default server and all virtual hosts together with their IP addresses and listening ports.

Furthermore, the list also contains an entry for each virtual host showing its location in the configuration files. Virtual hosts can be configured via YaST as described in Section All files in this directory with the extension. A basic template for a virtual host is provided in this directory vhost. It is recommended to always create a virtual host configuration file, even if your Web server only hosts one domain.

By doing so, you not only have the domain-specific configuration in one file, but you can always fall back to a working basic configuration by simply moving, deleting, or renaming the configuration file for the virtual host. For the same reason, you should also create separate configuration files for each virtual host.

When using name-based virtual hosts it is recommended to set up a default configuration that will be used when a domain name does not match a virtual host configuration. The default virtual host is the one whose configuration is loaded first. When Apache receives a client request for a defined virtual host, it uses the directives enclosed in this section. Almost all directives can be used in a virtual host context.

With name-based virtual hosts, more than one Web site is served per IP address. Apache uses the host field in the HTTP header that is sent by the client to connect the request to a matching ServerName entry of one of the virtual host declarations.

If no matching ServerName is found, the first specified virtual host is used as a default. The opening VirtualHost tag takes the IP address or fully qualified domain name as an argument in a name-based virtual host configuration.

A port number directive is optional. When using IPv6 addresses, the address must be included in square brackets. This alternative virtual host configuration requires the setup of multiple IP addresses for a machine.

One instance of Apache hosts several domains, each of which is assigned a different IP. The physical server must have one IP address for each IP-based virtual host. If the machine does not have multiple network cards, virtual network interfaces IP aliasing can also be used. The following example shows Apache running on a machine with the IP A separate VirtualHost block is needed for every virtual server. Here, VirtualHost directives are only specified for interfaces other than When a Listen directive is also configured for At least the following directives should be in each virtual host configuration to set up a virtual host.

Path to the directory from which Apache should serve files for this host. For security reasons, access to the entire file system is forbidden by default, so you must explicitly unlock this directory within a Directory container. E-mail address of the server administrator. This address is, for example, shown on error pages Apache creates. The error log file for this virtual host.

Although it is not necessary to create separate error log files for each virtual host, it is common practice to do so, because it makes the debugging of errors much easier. The access log file for this virtual host. Although it is not necessary to create separate access log files for each virtual host, it is common practice to do so, because it allows the separate analysis of access statistics for each host.

As mentioned above, access to the whole file system is forbidden by default for security reasons. Therefore, explicitly unlock the directories in which you have placed the files Apache should serve—for example the DocumentRoot :. In previous versions of Apache, the statement Require all granted was expressed as:. When starting the module for the first time, the HTTP Server Wizard starts, prompting you to make a few basic decisions concerning administration of the server.

For more information, see Section In the last step of the dialog, you may enter the expert configuration mode to make even more specific settings. Here, specify the network interfaces and ports Apache uses to listen for incoming requests. You can select any combination of existing network interfaces and their respective IP addresses. Ports from all three ranges well-known ports, registered ports, and dynamic or private ports that are not reserved by other services can be used.

The default setting is to listen on all network interfaces IP addresses on port Keeping the port closed is only useful in test situations where no external access to the Web server is necessary. If you have multiple network interfaces, click Firewall Details to specify on which interface s the port s should be opened.

The Modules configuration option allows for the activation or deactivation of the script languages that the Web server should support. For the activation or deactivation of other modules, refer to Section Click Next to advance to the next dialog. This option pertains to the default Web server. As explained in Section The first declared virtual host in the configuration file is commonly called the default host. Each virtual host inherits the default host's configuration. To edit the host settings also called directives , select the appropriate entry in the table then click Edit.

To add new directives, click Add. To delete a directive, select it and click Delete. Path to the directory from which Apache serves files for this host. Using Alias directives, URLs can be mapped to physical file system locations. This means that a certain path even outside the Document Root in the file system can be accessed via a URL aliasing that path.

With Directory settings, you can enclose a group of configuration options that will only apply to the specified directory. It should not be necessary to change the defaults. With include, additional configuration files can be specified. With this directive, all files in this directory ending in. This specifies the default URL used by clients to contact the Web server. After finishing with the Default Host step, click Next to continue with the configuration.

In this step, the wizard displays a list of already configured virtual hosts see Section Server Resolution is used to determine how a host is identified name based or IP based. Clicking Next advances to the second part of the virtual host configuration dialog.

In part two of the virtual host configuration you can specify whether to enable CGI scripts and which directory to use for these scripts. It is also possible to enable SSL. If you do so, you must specify the path to the certificate as well. See Section With the Directory Index option, you can specify which file to display when the client requests a directory by default, index.

Add one or more file names space-separated to change this. It is not possible to add virtual hosts at will. If using name-based virtual hosts, each host name must be resolved on the network. If using IP-based virtual hosts, you can assign only one host to each IP address available. This is the final step of the wizard. Here, determine how and when the Apache server is started: when booting or manually. Also see a short summary of the configuration made so far.

If you are satisfied with your settings, click Finish to complete configuration. To change something, click Back until you have reached the desired dialog. The HTTP Server Configuration dialog also lets you make even more adjustments to the configuration than the wizard which only runs if you configure your Web server for the first time.

The following 6 NEW packages are going to be installed: apache2 apache2-prefork apache2-utils libgc1 system-user-wwwrun w3m The following recommended package was automatically selected: w3m 6 new packages to install.

Overall download size: 2. Already cached: 0 B. After the operation, additional 7. Configure Apache options as necessary. Test configured Apache options for errors. Restart apache2 service once you're done with yur configuration.