The Infrastructure-Team manages the DokuWiki server and makes sure all services like this wiki, the forums or the IRC logs are up and running.

Dennis Ploeger is working as a systems and network administrator for about fifteen years now, specialized in Linux systems administration and open source development. He's an Open Source enthusiast, but not religious – if the available Open Source thingies don't work, he won't use them just “because”. He worked with several linux distributions, but feels home in the debian-ish distributions. Bash-Scripting and “Piping”, Perl and PHP is naturally all in the package.

Frank Jørgensen has been working as a UNIX-admin for the past 12-13 years focusing on Linux system administration for the most part. He worked a couple of years at a largeish ISP where he got to know the usual suspects (apache, MySQL, Sendmail, Postfix, Bind etc…) and also did a bit of development work (mainly Perl, PHP and Bash). Red Hat (CentOS, Fedora) and SuSE is where he feels most at home - but he worked with other distros as well.

Christopher Smith doesn't have much formal Linux sysadmin experience, but regularly deploys web applications on Linux servers (predominantly Ubuntu on AWS these days) and keeps those sites operational. He's also an active DokuWiki developer for several years now.

Andreas Gohr worked for some years as a Linux system administrator and managed the old DokuWiki server on his own. He's trying to keep his role in the infrastructure team low to have more time for his other DokuWiki work.

Andrwe works as a system administrator since 2010. He learned Linux using Gentoo and now uses Arch Linux for all his systems and administrates debian-ish systems at work. He's specialized in Bash and has knowlegde about the usual stuff (apache, MySQL, Postfix, nginx, Lighttpd, Bind, etc…).

• Check apache and php error logs if there are any errors
  • we might have missed things on the move
  • if unsure ask at the mailinglist

• Optimize system monitoring ploeger
  • Integrate aacraid-status into Zabbix
• Setup a working backup system ploeger
  • Should work with Hetzner backup space
    • Access credentials are at /root/backup-access.txt
  • Keep a week of MySQL dumps
  • Backup all relevant data to restore the site
  • Standard unix formats (tar, gzip/ bzip) preferred over special backup formats
• Check if logrotate is setup for all webservices
  • increase keep time?
• Setup rootkit checks ploeger
• Setup system monitoring ploeger
  • Monitor load internally
  • Monitor service availability externally (can someone provide this?)
  • Internal alerts can go to admin@dokuwiki.org (forwards to all team members)
• Improve PHP error logging ploeger
  • currently goes to syslog (/var/log/messages)
  • each vhost should have it's own PHP error log
  • probably needs to have the fast cgi wrappers load an addtional php.ini (or use a command line switch for the PHP processor)
• Setup some notification on available package updates
  • we could use this script unless you know something better
  • regularly update the packages
• Setup SSL for the webserver ploeger
  • Do we need to use server name indication? adrianlang has some experience with it, if in doubt, contact him
  • Or would a wild card certificate for *.dokuwiki.org work?
  • andi will create a CACert certificate as soon as this is decided
  • SSL should be optionally available on all web services where users login (wiki, forum, bugtracker) done.
• Check if mails sent from the server are correct seems okay
• Change the firewall system to something better manageable. Perhaps something like http://www.shorewall.net/ changed to shorewall
• implement some scripts which automaticaly update the documentation of the server (package status, hardware, mainly this site: Server Setup ) – cronjob /etc/cron.daily/sysinfo.sh
• install and configure smartd

• serversetup
• backup
• rootkit
• monitoring
• dokubot