DeveloperWiki:Server configuration

From ArchWiki
Jump to navigation Jump to search

This page provides an overview of the Arch servers and their functions. Details can be found in the respective links for each server.

Main development server (formerly gerolde)

Tango-view-refresh-red.pngThis article or section is out of date.Tango-view-refresh-red.png

Reason: some services already moved to different hosts (Discuss in Talk:DeveloperWiki:Server configuration#)

This is a Dual-Xeon 2.8GHz server with 16GB of memory and a 2x300GB software RAID 1 array. It has been bought with Arch donation money and is currently located at velocity, who also donate the power and bandwidth. It runs a Xen hypervisor with the following hosts:

This is the Xen dom0 for the development server. It runs a Debian system with the Debian Xen kernel, as Arch does not maintain a stable Xen kernel. It has no public services. ssh access is limited to a small number of IP addresses and only Thomas, Aaron, Jan and Dale have access to it.

It bridges the physical ethernet interface with the virtual interfaces of the Xen domU instances and runs an IP-based firewall.

Legacy development server.

DNS aliases:

It offers the following public services:

  • ssh(openssh)
  • smtp(postfix): SMTP server for outgoing mail

This is the legacy web server. It runs Arch Linux with Arch's own kernel. Only developers who maintain web applications have ssh access. The ssh port is only open to gerolde.

DNS aliases:,,,,,

It offers the following public services:

  • http(apache): Hosts the following websites:
    • Main Arch website - uses python/django and a few static html pages
    • redirect to
    • Access to the git repositories - uses cgit
    • Feeds from Arch-related blogs - uses static html pages
    • Access to the packages and community subversion repositories - uses websvn
    • Bugtracker - uses flyspray(php)
  • svn(xinetd/svnserve): Public subversion access
  • git(xinetd/git-daemon): Public git access

Resource Allocation

Because this box is servicing multiple VMs, the resources allocated to each are not static. Here is how the box is currently divided up:

  • dom0: 512 MB RAM, 4 CPUs, 4GB disk
  • gerolde: 9493 MB RAM, 4 CPUs, 193 GB disk
  • gudrun: 6145 MB RAM, 4 CPUs, 30 GB disk

This is the main development server.

DNS aliases:,,,

It offers the following public services:

  • ssh(openssh): All developers and trusted users have ssh access to this machine.
  • rsync(rsyncd): Public mirrors (whitelisted by IP address) can synchronize the FTP directory. Anyone can synchronize the ABS tree.
  • smtp(postfix): SMTP server for the and domains
  • ``imap``(dovecot): IMAP server for local mail storage
  • http(nginx): All developers have direct access to the FTP directory via HTTP (static content only) - this is password-protected, users must use the mirrors.

Developers use this server to maintain the package repositories, the corresponding packages subversion repository and access the git repositories for their various arch-related projects.

  • nginx
    • Forums - uses fluxbb(php)
    • Arch Wiki - uses mediawiki(php)
    • AUR; website and GIT access
    • Mailing lists (mailman)
    • GPL and other sources repository

Releng server (alberich)

  • hardware: VPS donated by airVM, 125GiB LVM setup, 2GB ram, 1 core E5530 @ 2.40GHz
  • software: Arch Linux

This machine is meant for building installation images and hosting testbuilds and such. It runs no other services, because releng image building is "tricky stuff" best kept separate

The machine contains the releng environment, including chroots for each architecture.

DNS aliases:,

It offers the following public services:

  • ssh(openssh): All release engineers have ssh access to this machine.
  • http(lighttpd): To host releng files (testbuilds, custom repos/packages), no official media
  • bit torrent: Torrent tracker for the ISO

Build Server (celestia)

This is an Intel(R) Core(TM) i7-4770 CPU server with 32GB of memory. The machine is run by Ionut Biru (ioni). It runs Arch Linux.


It offers the following services:

  • ssh (openssh): Access to the build server is available to all Trusted Users and Developers on request.
  • Build server.
    • Each user is given access to a set of build scripts that simplify the build process for users with poor internet connections or lacking a 64-bit machine.


It offers he following services:

  • ssh: Access to the server for managing backups
  • storage for backups.

Other servers

We can always use more of course for our world domination plans! Right now our infrastructure is mostly contained to the above-mentioned servers, but there are a few specialty things running elsewhere.

This server is hosted on Dan's linode. It runs an instance of munin, which collects various stats from the servers in the domain. If you need access to any of this information and are a developer, get in contact with someone that does server administration[broken link: invalid section]. If you want an additional server added to the list, just ask.