Posted by Alex_007 on August 25, 2011 at 3:19pm
Hey everyone,
I'm new to the group and wanted to hear from anyone that has had experience setting up openpublish in a Microsoft environment? I have been going through the documentation and i noticed that it doesn't necessarily support IIS, or SQL - but there seems to be a multitude of patches. Anyone have any experience with this sort of setup? Am I wishful thinking?
Look forward to your feedback! Cheers,
AW
Comments
I've stood it up on IIS before
This isn't difficult to do.
Overall to set up OpenPublish on IIS, ust download the tar or zip, crack it open, put it whereever you keep websites, C:\www\ or whereever. Then go to IIS Manager and either create a new website or use the default one, right click and point it to the openpublish site files.
I would also strongly encourage you to use the Web PI to prepare the server before doing anything. Select the IIS Recommended Configuration, PHP 5.3, WinCache, PHP Manager and also MySQL if you don't have it. The easiest way to do all this is to install a Drupal app out of the web app gallery first then just delete the site. That will automatically install any dependencies you need with basically a few clicks.
After you've prepped the machine and created the new site in IIS everything else is the same, create your database, edit your config files, run install.php, etc.
After Drupal is installed, you also have to change the files and temp directory to place that IIS can have write access too. (sometimes OpenPublish will render funny or will not load pictures before you do this step). You can do this by navigating to the location in IIS Manager then clicking Explore on the very top right, then right clicking the directory, selecting properties, permissions then giving IUSR write access to the directory itself. You can also create a special user account to run the app pool in in Windows, then changing the identity for the app pool itself, then giving that user the permissions to write to those directories as well. This is probably preferred rather than using the standard worker process identity.
btw, one other thing, if you are using a remote MySQL machine I strongly encourage you to use IP and not named host. MySQL has a bug that makes name resolution terribly slow. IP avoids the issue altogether.
Hope this helps.
Mark
keep an eye out for wincache 1.1 bug. its a frustrating one.
http://groups.drupal.org/node/25535#comment-654488
www.johnbarclay.com