For the purposes of this page, we'll use the name New to refer to the servers hosted at Peer 1 (which are deleuze, mire, and eventually abulafia) and Old to refer to any servers that we've used previously.

Note: We are in the process of migrating people who have signed up as guinea pigs. We are not currently accepting new domain requests or providing help to non-guinea-pigs. This will change once we have made reasonable progress in working out the kinks of the new setup.

TableOfContents()

Getting login access to mire

For megacz to fill in.

Databases

Here lie interim dbtool docs until migration is done, at which time they will probably move to UsingDatabases.

To manage your database user and databases, the basic syntax is dbtool <DBTYPE> <COMMAND>, where <DBTYPE> is postgres or mysql.

The adduser command creates a database user for you, with the same name as your UNIX log-in name. In the case of mysql, you will be prompted for a password and confirmation re-entry in the usual manner.

The passwd command allows you to reset the password. (Useless for postgres, where we use only ident authentication)

The createdb <DBNAME> command creates a database named <USERNAME>_<DBNAME>.

DNS

We are purposely not sending any DNS data from New to Old, which means that you need to change domains at your registrar if you want New to be authoritative for them. The proper nameservers are ns1.hcoop.net and ns3.hcoop.net, in that order. Keeping ns.hcoop.net and ns2.hcoop.net will not work.

Domains

See the DomTool page for instructions on managing your domains with the new setup. The configuration files are in a vastly different format, but they have a better-defined syntax that should be relatively easy to understand.

Home

Your home directory is now managed by AFS. You will enter it by default when logging in to mire.hcoop.net via ssh. Type pwd to see what the path is. It will look like /afs/hcoop.net/user/u/us/username. Some directories have been created for you already, so that they have the correct permissions for things like serving web pages and delivering mail.

procmail

The page ProcmailExample has been updated for the new setup. Basically:

• Use the file ~/.procmail.d/procmailrc instead of ~/.procmailrc.

• Write any procmail logs in ~/Maildir rather than elsewhere.

• Use appropriate values for the HOME, MAILDIR, and DEFAULT options, based on those in ProcmailExample.

rsync

If you're using rsync to transfer data to the new servers, the "-a" option by itself won't work properly because rsync attempts to chgrp the transferred files. Use "-a --no-g" instead of "-a".