Created
September 3, 2009 19:15
-
-
Save dap/180477 to your computer and use it in GitHub Desktop.
Openfire to Prosody How-To
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
How to get sleekmigrate to work as noted at | |
http://el-tramo.be/blog/openfire-to-prosody-migration on Ubuntu 8.10: | |
0. Install python-tlslite from the chromium-daily PPA. | |
See https://launchpad.net/~chromium-daily/+archive/ppa. | |
1. Make a place to work: | |
$ mkdir ~/workspace && cd ~/workspace | |
2. Grab Remko's version of sleekmigrate, which contains | |
support for Openfire's Import/Export Plugin data format: | |
$ git clone git://el-tramo.be/sleekmigrate | |
3. Checkout a version of sleekxmpp from around the time that | |
Remko wrote his blog post (trust me): | |
$ svn co -r138 svn://netflint.net/sleekxmpp/trunk sleekxmpp | |
4. Checkout Remko's sleekmigrate-to-Prosody-data-dir script: | |
$ git clone git://el-tramo.be/xep227-to-prosody | |
5. Install the Openfire Import/Export plugin. Export your | |
user account information to user.xml and download that someplace. | |
6. Feed that to sleekmigrate: | |
$ cd ~/workspace/sleekmigrate | |
$ PYTHONPATH=../sleekxmpp ./sleekmigrate.py -o /tmp/users.xml -s your.server.hostname # doesn't work with DNS-aliased vanity domain | |
7. Feed sleekmigrate's output to xep-227-to-prosody.py: | |
$ cd ~/workspace/xep227-to-prosody | |
$ ./xep227-to-prosody.py ../sleekmigrate/227.xml /tmp/prosody | |
8. It's soup. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment