By ltwinner on

I've been developing my site in linux but this is no longer feasible for me as I have some applications that I have to run in windows for my job and I can't afford to keep rebooting into linux when I want to work on the site. So I want to move the development to windows for the moment so I can get some work done on it anytime I have some free time. When the site is ready to be launched I would like to move it back to linux.

So what does moving a drupal site from linux to windows entail? What steps should I go through?

⋅ Categories: Drupal 6.x

Comments

dheeraj.dagliya’s picture

dheeraj.dagliya commented

This should be straight forward if you have your windows environment configured (WAMP is installed) to host web applications.

Just create SQL file of your database and a zip file of your Drupal folder.
Move these two files into your windows environment, unzip your Drupal folder in your windows web folder, create new database using the SQL file. That should be all you need to do.

ltwinner’s picture

ltwinner commented

OK well, Ive moved the drupal folder to windows and imported the .SQL file into a blank .SQL file. And it is working in that my homepage now shows up. However if I click on any url links it goes to the phpmyadmin page. Here is the url in firefox when I click on a link that displays the phpmyadmin page:

http://localhost/drupal/node/72

Could it have something to do with clean urls being enabled in linux? How can I fix this?

EDIT: Fixed it by disabling clean urls

ThatSteveGuy’s picture

ThatSteveGuy commented

Clean URLs should work in windows. In IIS 6 I believe you will need an .htaccess utility like Isapi Rewrite. In IIS 7 I think it works natively. In the future, you might want to look into Web Platform Installer. It's pretty close to a push button Drupal installer for Windows.

elementweb’s picture

elementweb commented

I have just lost 3 hours of my time tracking down an error that was caused by a value set in the `variable` table.

Among the variables Drupal sets is the temp directory. I'm not sure why, but when registering CSS files, file_create_path identified the requested 'css' directory as being within the '/tmp' directory, which on the Windows server obviously does not exist. This caused drupal_build_css_cache to serve the file from the root '/css' directory, rather than the '/site/mysite/themes/mytheme/files/css' directory as it should have.