I'm not suggesting you change what your webservers run on, what was/is important to me is knowing what your workstation runs.
I would (strongly) suggest you test you changes on a local "development" server, then when they've been tested, export the changes to your "production" server. The simplest way to do that is to install
VirtualBox on
your workstation, create an Ubuntu VirtualMachine that is as close as possible to your "production" webserver, copy your "production" DokuWiki to your VirtualMachine "development" webserver (rsync); and then do your Drupal2DokuWiki conversions in your Ubuntu VirtualMachine (gives you access to
Pandoc, grep, sed, awk etc). It shouldn't take you more than 30 minutes to install VirtualBox and create an Ubuntu webserver - there is almost no learning curve required (click, read the screen, click, etc).
Converting from Drupal to DokuWiki is something that I'd do in a number of steps:-
1. Export the entire Drupal to a Linux environment. Use something like the
Static generator to do that. Put the entire static Drupal into a directory (in Ubuntu)
and back it up (e.g.
/home/rgleason/docs/drupal_original). Or use the previously given suggestion to use wget (sorry, can't remember offhand which of your recent threads I posted that to, and running out of lunch break).
2. Convert the static site (
~/docs/drupal_original) to DokuWiki format using Pandoc in situ. I've given an example, somewhere, in the forums previously (
man pandoc is the manual). To install Pandoc
apt-get install pandoc. You can recursively convert all the static Drupal site in one go (it'll only take a minute or two).
3. It's unlikely that the output will be perfect DokuWiki formatting
for style (links and plugin syntax is another step) - if you used a style manual to create the original Drupal content (and followed it) you can use that as a basis for a second pass at automating the DokuWiki formatting. If you didn't use/follow a Style manual you'll need to do some analysis of the required changes (ignore namespace layout, plugin syntax, and links for the time being) - use the playground in your "development" DokuWiki to see (
and note), what needs to be done. When you know what needs to be changed you can create a script that uses sed/awk/grep or perl to finish converting your Drupal static site into DokuWiki markup. Run the script, check that it works as intended, rinse and repeat as necessary.
4. Move the now converted text files into the appropriate namespaces beneath
$DokuWiki/data/pages (on your "development" webserver) renaming files as necessary (I've previously given you linux commands for doing that). This can be scripted, but you'll likely still have some corner cases that require user intervention.
5. Repeat the previous step with media.
6. Now use sed and grep to recursively apply plugin markup to
$DokuWiki/data/pages (on your "development" webserver). Test, rinse and repeat as necessary.
7. The finicky part will be importing changes that have been made to your "production" DokuWiki since you used it as the basis of your "development" DokuWiki. Judicious use of rsync would be my approach - after locking the "production" DokuWiki to prevent more changes. Test the "development" DokuWiki - getting someone else to also test is useful. When you're happy push the "development" version up to your "production" webserver.
Judging by your Drupal site I'd guess the entire process would take about a day, perhaps a little longer given that you would need to learn how to configure networking for VirtualBox (hint, choose "bridged"), basic rsync, grep and sed (search Stack Overflow, most of your questions are common ones). You'll find it's the testing and proofreading that will take the most time.