Talk:Server

From ArchWiki
Revision as of 14:33, 4 March 2009 by CB (Talk | contribs) (Structure)

Jump to: navigation, search

Content

I suggest we keep out all specific configuration and simply try to inform the reader of server-usefull applications. There are numerous well maintained articles on ssh, ssl, LAMP, cups, samba and other services you'd like to have on your server, so I suggest to simply list these applications one may want to have on his / her server (along with a basic explenation of the program / service and the use of it on a server). We can then link to the atricles already available.

This will prevent having several wikis on installing / configuring LAMP / cups and other server choises while still maintaining a complete server guide.

Comments?--stefanwilkens 19:50, 1 March 2009 (EST)

Structure

Restructure suggestion, not structured towards the role of the server (web / database / file / router etc.) but structured towards specific parts of a server, explaining the role and use of the specific service.

Introduction

In an IT environment servers are there to provide a service. These come in all shapes and sizes, the most common are webserver related which are covered below. These then work as a nice basis for additional services. Arch is essentially a naked operating system so more packages will need to be installed than for some other Linux server operating systems.

TO DO

  • Minimal required set-up (core installation + SSH for headless server)
  • Web Services
    • Apache
    • PHP
    • MySQL
    • SSL
    • E-Mail
    • FTP
  • Network Services
    • Cups
    • DHCP
    • Samba
  • Protection
    • iptables
    • denyhosts
    • SELinux
  • Server Adimistration
    • SSH
    • webmin
    • CUPS web interface
  • External Links

Comments?--stefanwilkens 19:50, 1 March 2009 (EST)

I would suggest a structure along the lines of this:

  • Initial Server setup (ie core arch install with ssh attached)
  • Standard LAMP setup (the current server wiki just does this bit but not much more imo) you may also want to add a bit about perl for this as some people will use perl rather than php and there are some useful tools that rely on perl for linux.
  • Include phpmyadmin (note it relies on php)

From here you will have a good base to install other features and those can be pick and choose features.

  • Recommend not using SELinux as tbh its a bitch, add a guide for it by all means tho.
  • Add backup protocols
  • Add monitoring
- Nmis
- possibly SNMP?