May 13, 2008
Setting Up A Development Environment for Deki Wiki
RobertM @ 4:51 pm
Hey devs! Want to write code for Deki Wiki? We just finished up some
step-by-step instructions on how to set up your very own development environment.
You’ll need Microsoft’s Visual Studio (for this set of instructions), and you’ll need to grab the VMWare-Certified MindTouch Deki Wiki Virtual Appliance (found here). After setting it up, the Virtual Machine has an “out-of-body experience”; the PHP and database layers are running in the VM while the API running inside of Visual Studio, allowing you to write code and test it on the fly. Go ahead, check it out and play!
categories: MindTouch





Nice writeup, but I could not get this to work.
I had trouble in 2 spots.
1. Where the instructions say, “Download the xml file (mindtouch.deki.startup.xml) from below”
Where? I tried to modify the one I found in the new trunck, but it was not correct.
2. Where the instructions say, “Lastly, in a web browser, go to http://IP_ADDRESS, where IP_ADDRESS is the IP of the Deki Wiki virtual appliance. You will see the DOS console screen in the Windows machine step through its’ processes, confirming that the Deki Wiki Linux virtual appliance is speaking to the API running in Visual Studio.”
wikidb - already exists if you are not starting with a fresh VMWare-Certified MindTouch Deki Wiki Virtual Appliance. Causing the setup to fail.
Comment by adam — May 14, 2008 @ 11:22 am
Hi there…
The correct XML file has been uploaded to the site, please check at the bottom of the page to download it.
As for the database, true, if you are not using a fresh virtual appliance as now stated at the top of the page (language updated, thanks!), then additional modifications would have to be made. MindTouch recommends using a fresh copy of the newest VM to make sure everything is functional and up-to-date.
Comment by RobertM — May 14, 2008 @ 11:35 am
Success! Thanks for the writeup.
2 quick questions: I actually was only able to get this going in my home environment.
Here at the office they like to make new development hard by blocking most ports. Should I be able to run this over a different port? Will I only need to change the areas mentioned in your documentation where port 8081 is referenced?
Thanks again.
Comment by adam — May 15, 2008 @ 5:57 am