Move exisiting site in web hosting provider to QuickStart for installing modules or apps

We encourage users to post events happening in the community to the community events group on https://www.drupal.org.
mapreferee's picture

I have created a site in web hosting providing using simple script. And several months later, I found Quickstart which is extremely handy for site development on ubuntu platform.

I wonder if I can use Quickstart to manage my exisiting sites that is already built and hosted somewhere else?

Comments

We had the same question!

TransitionKojo's picture

I gave a short presentation at our DUG in Houston and someone asked similar question. I'd be curious to know if/how this could work.

Moving old sites to quickstart

MichaelCole's picture

Hi Transition, this is a common question, and it doesn't have a simple answer.

Quickstart is several things, integrated into one package:
1) A LAMP server
2) A set of pre-configured tools for debugging (Netbeans + XDebug, etc)
3) A few drush commands to reduce repetitive work.
4) Pre-configured and downloadable as a virtual machine.

An older project can be moved onto the LAMP server, like any other PHP project. Configure DNS, Apache, MySQL, and settings.php to point to mysql. This requires understanding how LAMP servers are configured to run projects.

Once the older project is in the LAMP server, the debugging tools should work.

Unfortunately, the drush commands can't figure it out without a human understanding it. There is not yet a common standard for packaging a php website for deployment.

What you can do is look at this: drush help quickstart-create

This will show all the options for quickstart-create and get you on your way. Remember you need to setup dns, apache, mysql, and the code. If you're bringing in an old site, you might:

1) create a folder ~/websites/oldsite.dev
2) copy the site's files into oldsite.dev
3) drush quickstart-create dns apache mysql --domain=oldsite.dev
4) (import the site's sql into the database oldsite_dev)
5) edit sites/default/settings.php to point to the oldsite_dev database (user and password are also oldsite_dev)
6) Point a browser at oldsite.dev to test

Mike

anissa2017@yahoo.com's picture

Hello Dear

My name is Anissa B. Cufon in search of one who understands love as trust and faith rather seeing it as a way of fun, reading about you i develop interest on you, please reply me with this mail box ( anissa2017@yahoo.com ) and dont reply me on this site as may not check on this site,i believe we can start from here, waiting for your reply so that i can send my pictures and further introductions.
kisses Anissa B. Cufon .

email box ( anissa2017@yahoo.com )

Hello Dear

My name is Anissa B. Cufon in search of one who understands love as trust and faith rather seeing it as a way of fun, reading about you i develop interest on you, please reply me with this mail box ( anissa2017@yahoo.com ) and dont reply me

several sources that look useful

mapreferee's picture

I also googled a little bit about how this can be done and found two articles that might add value to MichaelCole's informative reply.

They are:

_____________________________________
1. Quick Drush Tip – Import database SQL with drush sql-cli (sqlc) by By WIZONE SOLUTIONS | Published: MARCH 28, 2011
http://www.wizonesolutions.com/2011/03/28/quick-drush-tip-import-databas...

2. How to move a Drupal site from one host to another Drupal Hosting and Installation by anonymous
http://support.hostgator.com/articles/hosting-guide/publish-your-site/ho...

_______________

Hope they can be helpful

Indeed, I tried what MichaelCole said. Everything went smoothly until when I tested the site. A warning message pops up, saying "failed to open stream: "DrupalTemporaryStreamWrapper::stream_open" call failed in file_create_htaccess() (line 5............"

I read the post http://drupal.org/node/1076762. It seems that they encountered the same problem and had it solved. But frankly, I dont know what they meant. Keep working on this issue.

---------------------updates on 8 Oct 2011--------------------------
I found a solution from https://help.ubuntu.com/community/Drupal#Write_Access

By typing the following commands:

sudo chown www-data:www-data -R /home/quickstart/Desktop/websites/mysitename.dev
sudo chown www-data:www-data -R /home/quickstart/Desktop/websites/mysitename.dev/tempdir
sudo chown www-data:www-data -R /home/quickstart/Desktop/websites/mysitename.dev/sites/default/files

Then, the warning message ""failed to open stream: "DrupalTemporaryStreamWrap...." will be gone and Im stoked.

If you want to change the permission of a certain file that is locked (e.g. template.php), you can go to its location and type:

sudo chmod 777 filename

You will change its permission to read ad write for owner, groups and others (in my case they are all www-data). And now you can edit and save the file very easily.

I know this might sound stupid to some experienced drupal people here. But to those who are newbies like me and show interest in learning this stuff, hope they find it useful.

Also, all those things I wrote in this comment are only based on my understanding from desktop search and personal experiment on ubuntu. So, it may not be the best method. Please correct me if Im wrong.

rsync + sql-sync

jedihe's picture

If I understand correctly your need, a superb solution could be using drush rsync and drush sql-sync. If you have shell access to your hosting service, it's very easy to configure an alias for the remote site and one for a local "stub" site (created with qc instead of configuring everything by hand). Having these will make very easy to move changes from any site to the other (live to dev, dev to live):

  1. SSH keys appropriately set up. See: http://thedrupalblog.com/setting-passwordless-automated-rsync-backup (just the setup for passwordless auth)
  2. aliases.drushrc.php with the appropriate aliases for the sites. See: http://drupal.org/node/670460
    I also recommend doing drush selfupdate on quickstart to get drush 4.5, which includes the command arb (for doing fast and easy backups).

WARNING: BACKUP YOUR SITE BEFORE STARTING TO USE THESE, AS THEY INVOLVE SOME DESTRUCTIVE OPERATIONS.

Jehv