Updating Local Environment.html - pabloviquez/docutest GitHub Wiki

Starkey Foundation - Starkey Video : Updating Local Environment

This page last changed on Jul 22, 2014 by pablo.viquez.

Main Navigation

Home

Home - Development

Home - Discovery & Architectur- e

Home - Servers & Sysadmin

Home - Starkey Teaser

Development Menu

API Specificati- on

Brightcove Documentati- on

Expression Engine Core Changes

Expression Engine DB

Home - Development

Local Environment Setup

Notes & Development priorities

Points Flow

QA - Remote Debugging

Server Side Debugging

Server Side Models

Starkey Social Networks Accounts

Updating Local Environment

URLs, Views & Data Models

Updating Local Environment

In the case of updating the local environment with someone else data, please follow these steps:

(1) Update your code repository

Update the trunk and sysadmin directories, then navigate to it.

> cd data
> svn up operationchange_trunk sysadmin

(2) Re-Populate the DB with the new data

For this step, you need to run the latest SQL dump, you can easily find out by running this command on the terminal:

vagrant@precise64:~$ cd data/operationchange_trunk/sql/staging/
vagrant@precise64:~/data/operationchange_trunk/sql/staging$ ls -lt |awk 'NR < 3 { print $9 }' |awk 'NR > 1'

Once having the latest SQL dump, execute the following:

vagrant@precise64:~/data/operationchange_trunk/sql/staging$ mysql -uroot -p123456 starkey
mysql> \. LATEST SQL FILE FROM PREVIOUS STEP.sql

Migrating SVN Repository

Any code development after 2014-03-04 needs to happen under a new repository.

How to migrate your old repository

If you're using the Vagrant virtual machine follow these easy steps:

Useful Reading
Even though you can follow these steps and you're done, it's highly recommended that you read and understand what you're about to do:<http://svnbook.red- bean.com/en/1.7/svn.ref.svn.html#svn.ref.svn.sw.relocate>

svn switch

 --relocate
    Deprecated. When used with the svn switch subcommand, changes the location of the
                repository that your working copy references. The preferred approach as
                of Subversion 1.7, however, is to use the svn relocate subcommand.

Directories to upgrade: operationchange_trunk, sysadmin & teaser

TEASER UPGRADE

$ cd data
$ cd teaser_trunk
$ svn info
Path: .
URL: https://repo.schematic.com/svn/starkey/teaser/trunk
Repository Root: https://repo.schematic.com/svn/starkey
Repository UUID: 4ca7ef10-3506-11e3-a7cb-999016a4c4ee
Revision: 682
Node Kind: directory
Schedule: normal
Last Changed Author: pviquez
Last Changed Rev: 275
Last Changed Date: 2014-01-14 18:46:06 -0600 (Tue, 14 Jan 2014)

Now, lets do the switch:

$ svn switch --relocate \
https://repo.schematic.com/svn/starkey/teaser/trunk \
https://svn.cr.possible.com/svn/starkey/teaser/trunk

$ svn up

$ svn info
Path: .
URL: https://svn.cr.possible.com/svn/starkey/teaser/trunk
Repository Root: https://svn.cr.possible.com/svn/starkey
Repository UUID: 4ca7ef10-3506-11e3-a7cb-999016a4c4ee
Revision: 688
Node Kind: directory
Schedule: normal
Last Changed Author: pviquez
Last Changed Rev: 686
Last Changed Date: 2014-03-14 10:03:17 -0600 (Fri, 14 Mar 2014)

SYSADMIN UPGRADE

$ cd data
$ cd sysadmin
$ svn up
$ svn info
Path: .
URL: https://repo.schematic.com/svn/starkey/operationchange/sysadmin
Repository Root: https://repo.schematic.com/svn/starkey
Repository UUID: 4ca7ef10-3506-11e3-a7cb-999016a4c4ee
Revision: 682 <- Make sure this is the
           revision in your local
           instance
Node Kind: directory
Schedule: normal
Last Changed Author: pviquez
Last Changed Rev: 505
Last Changed Date: 2014-02-24 10:57:14 -0600 (Mon, 24 Feb 2014)


$ svn switch --relocate \
https://repo.schematic.com/svn/starkey/operationchange/sysadmin \
https://svn.cr.possible.com/svn/starkey/operationchange/sysadmin

$ svn up

$ svn info
Path: .
URL: https://svn.cr.possible.com/svn/starkey/operationchange/sysadmin
Repository Root: https://svn.cr.possible.com/svn/starkey
Repository UUID: 4ca7ef10-3506-11e3-a7cb-999016a4c4ee
Revision: 688 <- Make sure this is the
            revision in your local
            instance
Node Kind: directory
Schedule: normal
Last Changed Author: pviquez
Last Changed Rev: 688
Last Changed Date: 2014-03-14 10:06:26 -0600 (Fri, 14 Mar 2014)

OPERATIONCHANGE_TRUNK UPGRADE

$ cd data/
$ cd operationchange_trunk
$ svn up
At revision 682.

$ svn info
Path: .
URL: https://repo.schematic.com/svn/starkey/operationchange/trunk
Repository Root: https://repo.schematic.com/svn/starkey
Repository UUID: 4ca7ef10-3506-11e3-a7cb-999016a4c4ee
Revision: 682
Node Kind: directory
Schedule: normal
Last Changed Author: gloriana.zamora
Last Changed Rev: 682 <- Make sure this is the
                revision in your local
                instance
Last Changed Date: 2014-03-13 18:05:09 -0600 (Thu, 13 Mar 2014)


$ svn switch --relocate \
https://repo.schematic.com/svn/starkey/operationchange/trunk \
https://svn.cr.possible.com/svn/starkey/operationchange/trunk


$ svn up

$ svn info
Path: .
URL: https://svn.cr.possible.com/svn/starkey/operationchange/trunk
Repository Root: https://svn.cr.possible.com/svn/starkey
Repository UUID: 4ca7ef10-3506-11e3-a7cb-999016a4c4ee
Revision: 688
Node Kind: directory
Schedule: normal
Last Changed Author: gloriana.zamora
Last Changed Rev: 682 <- Now your local
              instance should be @
              this rev
Last Changed Date: 2014-03-13 18:05:09 -0600 (Thu, 13 Mar 2014)

How to update paths on Expression Engine?

In the admin, go to Tools ? Data ? Search and Replace and select the Site Preferences database. You will be able to search and replaces configuration paths all at once.

How to upgrade your SVN binaries on MAC

The following steps are for updating the SVN binaries on MAC.

Requirements

  • Have installed Homebrew
  • Know what version of SVN have insalled

Install SVN using homebrew

> brew install svn

Upgrade SVN latest version (assuming 1.8.8 is the latest version)

> brew install svn
> cd /usr/bin
> ln -sF /usr/local/Cellar/subversion/1.8.8/bin/* .
> exit

Downgrade SVN to 1.6.17 version

> cd $( brew --prefix )
> git checkout 6e2d550 Library/Formula/subversion.rb
> brew install svn

Fix TAR issue with BSD

By default, MAC has BSDTAR as the default program for tar files, however BSD, is not compatible with it. To change the tar version to gnutar do:

brew install gnu-tar
cd /usr/bin
sudo ln -sF /usr/local/opt/gnu-tar/libexec/gnubin/gnutar tar

Migration Steps Checklist

Migration Tasks

87% of the tasks completed

Review new repository, see latest version and compare it with the old one

Medium

Make a copy of the repo locally and make switch --relocate

Medium

Commit something, revert the revision and commit again

Medium

Create a branch, a tag and merge something

Medium

Update the sysadmin scripts to point to the new location

Medium

Update confluence any reference to the old repo

Medium

Send a detail email with the steps required for migration

Medium

Upgrade QA server

Medium

In This Page

  • Updating Local Environment
    • (1) Update your code repository
    • (2) Re-Populate the DB with the new data
  • Migrating SVN Repository
    • How to migrate your old repository
    • Directories to upgrade: operationchange_trunk, sysadmin & teaser
      • TEASER UPGRADE
      • SYSADMIN UPGRADE
      • OPERATIONCHANGE_TRUNK UPGRADE
    • How to update paths on Expression Engine?
    • How to upgrade your SVN binaries on MAC
    • Fix TAR issue with BSD
  • Migration Steps Checklist
    • Migration Tasks
      • 0% of the tasks completed

Site Map

Document generated by Confluence on Sep 16, 2014 14:12