As I’ve been blogging about, I’ve been playing a lot with Apple’s new WikiServer (or “Teams Server”) at work. We’re still evaluating what we’d like to use it for, but as part of the experiments, I’ve been finding myself having to do some pretty crazy things with the WikiServer. This one is pretty bizarre, and is probably not only very dangerous for the content of your group’s wiki and blog, but also almost certainly not a best-practice.
With that caveat out of the way, here’s how I managed to move all the pages in an Apple WikiServer group wiki and blog from one group to another.
Dear God, please have a backup!
Okay, step 1 is mundane, but seriously, please of please have a backup of your data before you do any of these things. To make a back up of your entire WikiServer’s data store, simply:
sudo tar -cvzf backup-file-name.tgz /Library/Collaboration
If anything goes wrong, you can restore from your backup just as simply:
sudo tar -C /Library/Collaboration -xvzf backup-file-name.tgz
Okay, with that out of the way, next make sure absolutely nobody is using any of the Group services for the group you are going to perform the move from, or to. People can work on other group’s wikis, it’s just the ones you’ll be touching you want people to avoid. You can enforce this with some Apache redirects, which is left as an exercise to the reader.
Step 1: Rename or create a new Group in Workgroup Manager
First, you need to either rename or create a new group in Workgroup Manager. If you make a new group, be sure to enable all the services that the old group used.
If you’re simply renaming a group, then you might not even have to go through this trouble. You merely need to change the group’s “Name” (as opposed to its “Short Name”) and then stop and start the Web Service from Server Admin to see the group’s name change. However, if you also want to change the group’s “Short Name” (i.e., the group’s POSIX group account symbolic name), then you will need to perform these steps.
Once you have the new group ready to go in Workgroup Manager and you have stopped and started your Web Service in Server Admin, continue to the next step.
Step 2: rsync all your files from the old group to the new group
This is simple. Just run:
sudo rsync -avzE --progress /Library/Collaboration/Groups/old-group/ /Library/Collaboration/Groups/new-group/
Note that the trailing slashes on the directory names in this command are quite important, as they tell
rsync to take the contents of the first directory and place those items as the contents of the second directory. Without the trailing slashes,
rsync will make extraneous directories for you, which Apple WikiServer won’t understand. See
man rsync for more information.
Step 3: Update the
plists for all your WikiServer pages in the new group
Now, WikiServer has all the content of your old group but all of the internal references are wrong, since they still point to the old group. What you need to do is rewrite all those references so that they point to the new group address. The group references are stored in property list files. See my older blog entries for details about the filesystem structure of Apple’s WikiServer data storage layout.
To do this is a relatively simple procedure. As root, do the following, and do it carefully because as root you can easily mess up (and there is no undo button on the command line!):
sudo su - cd /Library/Collaboration/Groups/new-group grep -ri "old-group" * | grep '^[^B]' | cut -d ':' -f 1 | grep 'plist$' | sort | uniq > /tmp/list_of_plist_files_to_edit for i in `cat /tmp/list_of_plist_files_to_edit`; do sed -e 's/<string>groups\/old-group/<string>groups\/new-group/' $i > $i.new; mv "$i.new" "$i"; chown teamsserver:teamsserver "$i"; chmod o-rwx "$i" done;
In English, this means:
- Become root.
- Change to the
- Find all
plistfiles that have the the string old-group in them, sort them, and write this list of files to the
- For each of the files listed in the
/tmp/list_of_plist_files_to_edit, find the text string
<string>groups/old-groupand replace that text with
<string>groups/new-group, and save this change as the name of the file with
.newappended. Finally, replace the original file with the file we modified, and give them the appropriate permissions.
Step 4: Create an Apache redirect to make sure no HTML links are broken
Okay, at this point your new group is up and running and it should be working. However, if you had any links at all in any of your group’s pages, they are now all broken because they still point to the old group. Rather than going through the HTML itself and cleaning this up right now (because that’s very error-prone indeed, even with automated tools), it’s much easier to just tell Apache to redirect all requests for the old group to the new group.
To do this, edit the Apache configuration file of whatever Virtual Host you have been serving the WikiServer from. Most of the time, this will be at
The end of that file probably looks something like this::
# Include /etc/httpd/httpd_users.conf # Include /etc/httpd/httpd_directory.conf Include /etc/httpd/httpd_groups.conf Include /etc/httpd/httpd_teams_required.conf LogLevel warn ServerAlias * </VirtualHost>
Right above these
Include directives, simply add the following:
<Location /groups> <IfModule mod_alias.c> Redirect 301 /groups/old-group http://your.server.address/groups/new-group </IfModule> </Location> # Include /etc/httpd/httpd_users.conf # Include /etc/httpd/httpd_directory.conf Include /etc/httpd/httpd_groups.conf Include /etc/httpd/httpd_teams_required.conf LogLevel warn ServerAlias * </VirtualHost>
There you have it. New Teams Server group, old group’s data.
Note that this does not update any of the SQLite databases used to store things like revision history and so forth. These things are, for the most part, not really necessary to update but it would be ideal if the old
plist revisions could be changed in there, too. That’s not so much more extra work, really, but I’ve found it typically unnecessary except in fringe cases, so I leave that as an exercise to the reader.
If you do this to your WikiServer and do not update the SQLite databases as well, just be mindful of that fact so that you’re not surprised if something goes wonky down the line.