A guide to migrating your services to bog.

<<TableOfContents>>

== Explanation of New Machines ==

Debian squeeze, firewall, AMD64.

Because of openafs, this isn't really a "migration", but merely setting things to run on different nodes.

== Firewall ==

With the restrictive firewall in place, you will have to request rules if you need to access Internet resources from your cgi programs, or want to use irc or similar from bog.

FirewallRules

== Moving Web Sites ==

Static web sites will work on navajos without any special effort, but if you're using cgi you will probably have to request packages.

(Mention domtool-tail for checking error logs, since it's hidden well in the manual)

=== Easy Domain Users ===

To test migration, ...

To migrate everything, set `DefaultWebNode = "navajos"` in your `dom` config.

=== Low-level domain users ===

You're on your own ;-)

=== Proxied Servers ===

Proxied servers must be run on bog. Request ProxiedServer firewall rule. Cron permissions for starting at reboot.

If you are running your own instance of Apache on mire, please file a bug report explaining why you are doing so. If it's just to run a newer version than available on mire, you can probably just switch to the system-wide version. If you need modules or directives not supported by DomTool, any that can be supported securely will be added during migration.

=== PHP ===

If you are using php4, you must upgrade to php5. 

== Databases ==

MySQL users should not need to do anything.

Postgres users will need to dump their databases and upgrade to 9.1. New dbtool "database" `postgres-9.1`. If any trouble is encountered, file a bug under SQL DBs.

== Using the New Shell Server ==

Just `ssh $user@bog.hcoop.net`

== HCoop Services ==

Document temporary squirrelmail/roundcube addresses