hi,

I'm loving drupalpro, yet i'm having some troubles moving from my virtualbox into production.

these are the steps i take -

  1. create a DB and a user name in the server
  2. export the DB from DrupalPro and import it into the server
  3. archive the website folder in DrupalPro and upload it to the server
  4. Extract the archive to the server public_html
  5. here comes the hard part - i need to update the permission (640 --> 644) and the owner/group
  6. update the settings.php to the new DB
  7. rinse and repeat each time i make changes in DrupalPro

now, it works, but it doesn't look like the best practice to me, and i'm eager to learn what the pros are doing.

any thoughts?

Comments

mike stewart’s picture

mike stewart CreditAttribution: mike stewart commented

glad you're liking. I'm not sure I have the perfrect answer for you,,, as it tends to vary on each of our projects... but yes, the initial project setup is always a bit of a small chore.

What we do for the sites that live on our staging server is:

  1. use a script to setup apache vhost & setup empty db for each project.
  2. then setup GIT (we clone bare, copy it to out side root and setup a hook to push) <-- optional
  3. setup drush group alias in sites/all/drush
  4. drush rsync @foobar.local @foobar.stage
  5. drush sql-sync @foobar.local @foobar.stage

Note: If you have a database user on the server that has permissions to create a database, instead of doing all of step one, you can run: drush sql-sync --create-db @foobar.local @foobar.stage

Also note, our plan is not to keep doing this for much longer... but more about that later. ;-)