Page History

...

* it does not work with a domain name here!

...

How to get yourself set up to use the scripts

• do this on each machine (victoria01, victoria02, victoria03)

      cd ~
      git clone git@github.com:cul-it/drupal-site-moves.git
  

How to change the modules and themes

• if the drush.make file is in git
  • it will likely be in github in cul-it in a repository named after the site
    • eg. www-library-cornell-edu corresponds to www.library.cornell.edu
  • clone the repo to your local machine to do the updates, then check back in on the master branch
• if the drush.make file is in subversion
  
  • do a subversion checkout of https://svn.library.cornell.edu/cul-drupal
• • find your make file under cul-drupal/[drupal_6 or drupal_7]/make/[your site name]/[your site name].make
• add lines or modify the version of the module listed according to the drush make file format (use other sites for examples)
• check in the changed version

...

• go to victoria02 and cd /libweb/sites/[your site name]/make
• dr-make.sh @[your site name]

• Panel
  Note: the alias argument @[your site name] is no longer necessary for dr-make.sh

• a few sites on victoria02 use drush.make files stored in git
  • use ~/drupal-site-moves/dr-make-git.sh for these
  • main1.test.library.cornell.edu

How to update your theme/module code on the site

...

• You need to have ssh keys set up so you can get to the other machine without a password prompt
• one easy way to do this is set up the drush command 'pushkey'
  
  • read all about it: https://www.drupal.org/project/drush_extras

  • PUSHKEY
    
        drush pushkey user@host.domain.com
    
    	Creates an ssh public/private key pair in $HOME/.ssh, if
    	one does not already exist, and then pushes the public
    	key to the specified remote account.  The password for the
    	destination account must be entered once to push the
    	key over; after the key has been stored on the remote
    	system, subsequent ssh and remote drush commands may be
    	executed using the public/private key pair for authentication.
    
    	IN DRUSH EXTRAS because is is Linux / openssl-specific.
            

  • install it in your user's drush
    • log in to victoria02

    • drush dl drush_extras

  • use it

    • log in to victoria02
    • drush pushkey nid123@victoria01.library.cornell.edu
    • prompts for password on victoria01 one time
    • now try
      • ssh nid123@victoria01.library.cornell.edu
      • no password prompt, right?

once the ssh keys are set up, you can avoid lots of extra 

Enter passphrase for key '/home/user/.ssh/id_rsa'

prompts by using this command:

ssh-add

See this: http://blog.joncairns.com/2013/12/understanding-ssh-agent-and-ssh-add/

How to get the latest versions of the scripts

...