Lets discuss Apache under arch!

Haikarainen · 2012-09-26 17:28:31

As a relatively new Arch-user(but still longtime linux-user mainly under Debian), I set out to setup a small local development-server consisting of mainly apache and mysql, and since I own a few domain-names, I was also going to set up some virtual hosts for certain subdomains.

While I rushed into doing this after installing apache and configuring systemd for it, I noticed my dear and beloved /etc/apache/sites-* and /etc/apache/modules-* system where nowhere to be found. I am met with a completely different system that reminds me more of the older almost single httpd.conf file, and a symlink to a modulesdir, all under /etc/httpd/ (!?).

This kind of setup is completely new to me, before if I wanted a virtual host, I just added a file to a directory and voila. Now I have to add every single virtual host into a single file!? On my old debian server I think I have like 10 different vhosts. If I wanted to activate an apache module I just created a symlink from /modules-available to /modules-enabled.
This is currently the biggest "issue" I wanted to duscuss, anyone who knows this system can you please share your thought on what I am supposed to do with it, what are the comfortable bits of this, and is it possible to revive parts of the old setup?

Also regarding the httpd-directory; With this thinking, what if I install another http-service I want to co-exist with apache, on another port? What would /etc/httpd/ contain? This part is just plain stupid to me right now.

The next issue: The new /srv-layout. It used to be /var/www and ~/www/ . Now I have a completely new rootfolder(something that seems to clutt it up even more actually, even though a www in /var was a little ugly.) Is /srv/ something I should just get used to?

Thanks for any thoughts on the matter!

fukawi2 · 2012-09-26 22:57:27

Haikarainen wrote:

This kind of setup is completely new to me, before if I wanted a virtual host, I just added a file to a directory and voila. Now I have to add every single virtual host into a single file!? On my old debian server I think I have like 10 different vhosts. If I wanted to activate an apache module I just created a symlink from /modules-available to /modules-enabled.

As someone with an RedHat and Arch background, I find the Debian way of Apache config arcane and annoying

Haikarainen wrote:

This is currently the biggest "issue" I wanted to duscuss, anyone who knows this system can you please share your thought on what I am supposed to do with it, what are the comfortable bits of this, and is it possible to revive parts of the old setup?

Personally, as far as vhosts go, I create /etc/httpd/vhosts/ to hold a config file for each vhost, then create /etc/httpd/conf/extra/vhosts.conf that sets up the virtual hosting config, and includes vhosts/*

Haikarainen wrote:

The next issue: The new /srv-layout. It used to be /var/www and ~/www/ . Now I have a completely new rootfolder(something that seems to clutt it up even more actually, even though a www in /var was a little ugly.) Is /srv/ something I should just get used to?

That's a long on-going debate in the Arch community. When you compare the FHS definition of each path, it does make sense to have your webroot(s) in /srv

/var = Variable files—files whose content is expected to continually change during normal operation of the system—such as logs, spool files, and temporary e-mail files.
/srv = Site-specific data which are served by the system.

progandy · 2012-09-27 00:20:42

Haikarainen wrote:

Also regarding the httpd-directory; With this thinking, what if I install another http-service I want to co-exist with apache, on another port? What would /etc/httpd/ contain? This part is just plain stupid to me right now.

Isn't httpd mainly used for apache, while all other servers use different names for directories and files?

The next issue: The new /srv-layout. It used to be /var/www and ~/www/ . Now I have a completely new rootfolder(something that seems to clutt it up even more actually, even though a www in /var was a little ugly.) Is /srv/ something I should just get used to?

You can modify the paths in the configuration file to your liking, /srv is a sane default value.

Arch Linux

#1 2012-09-26 17:28:31

Lets discuss Apache under arch!

#2 2012-09-26 22:57:27

Re: Lets discuss Apache under arch!

#3 2012-09-27 00:20:42

Re: Lets discuss Apache under arch!

Board footer