Category talk:Web server

From ArchWiki
Jump to: navigation, search

These ain't web servers

Putting anything that requires or extends a web server in the web server category is stupid.

I therefore propose the following creation of categories and recategorization.

Web server
Apache HTTP Server, Caddy, Hiawatha, Lighttpd, nginx, Tomcat, UWSGI, Varnish, webfs
Web applications
Awstats, Diaspora, Gallery2, Moodle, Multi Router Traffic Grapher, cgit
Apache

Irrelevant: Chef, Fhem, Jekyll, Jenkins, Server, Subversion, XAMPP, Tryton
To be archived: Ampps, EAccelerator, Habari, IspCP

--Larivact (talk) 14:17, 1 July 2017 (UTC)

Good idea, but why is XAMPP in "Web server" but Apache and FastCGI et al have a separate category? I think they should be merged into simply "Web server". File sharing and synchronization are also arguably irrelevant to a web server, though they could have a separate category. Anyway, this overlaps with Talk:List of applications#Radical alternative, it would be best to solve them at the same time. -- Lahwaacz (talk) 17:46, 1 July 2017 (UTC)
I think you misunderstood. The definition terms represent new categories, and the descriptions their pages. Everything not listed under web server gets removed from the "Web server" category. I only put the Apache pages in a list to improve readability. I agree that XAMPP shouldn't be in "Web server". --Larivact (talk) 18:24, 1 July 2017 (UTC)
I think I understood that, so let me reformulate. I don't understand why Apache HTTP Server should stay in the "Web server" category, but all other pages related to Apache should get another category (called "Apache" above), which does not include the Apache HTTP Server, although it's clearly relevant. I think that all pages you listed under "Apache" should stay in the "Web server" category - if it's not clear from the title that they are Apache-only, maybe they should be renamed, e.g. mod_gnutls -> Apache HTTP Server/mod_gnutls etc. I think it's fairly common that subpages share the same category with the master page. -- Lahwaacz (talk) 19:34, 1 July 2017 (UTC)
Yeah making the Apache-specific articles subpages of Apache HTTP Server would clarify the "Web server" category but "Apache HTTP Server" is in my opinion too verbose for a subpage prefix. Maybe we should rename Apache HTTP Server to Apache or httpd? Both would however confuse people. --Larivact (talk) 19:45, 1 July 2017 (UTC)
I like this plan, if a decision on an "Apache HTTP Server" prefix is the only blocker, why not apply it only to mod_gnutls, mod_perl, mod_python, mod_wsgi for the moment, and see what the end result looks like: it wouldn't be the longest prefix in the wiki, for example we have Dual boot with Windows/SafeBoot or Advanced Linux Sound Architecture/Example Configurations, and these read perfectly fine to me. -- Kynikos (talk) 16:02, 6 July 2017 (UTC)
Long subpage prefixes harm readability. You have to agree that ALSA/Example Configurations is more readable. The problem is that MediaWiki doesn't support contracted subpage prefixes. --Larivact (talk) 16:38, 6 July 2017 (UTC)