appirio-tech/tc1-mf-vagrant

Name: tc1-mf-vagrant

Owner: Topcoder

Description: Vagrant environment for topcoder member facing site.

Created: 2014-11-27 01:54:44.0

Updated: 2016-12-11 20:44:34.0

Pushed: 2016-06-08 13:28:56.0

Homepage: null

Size: 13

Language: null

GitHub Committers

User	Most Recent Commit	# Commits

Other Committers

User	Email	Most Recent Commit	# Commits

README

tc1-mf-vagrant

Vagrant environment for topcoder member facing site.

Prerequisites:

Virtualbox: https://www.virtualbox.org/wiki/Downloads Vagrant: https://www.vagrantup.com/downloads On MacOS, osxfuse is required: http://osxfuse.github.io/ or brew install sshfs

Installation:

• Clone this repo
• Inside the folder repo, run the following commands: (Please note, the 'vagrant up' command is a 1GB download)

ant plugin install vagrant-sshfs --plugin-version=0.0.6 #need old version
ant up --provider=virtualbox #to bring up the VM
ant ssh #to ssh to the VM

• The tc-site directory on the vagrant machine maps to the ~/tc-env on your host

• machine by default, so you should clone the tc-site repo to your ~/tc-env folder.

• Alternatively, you can modify the localTCSite variable in the Vagrantfile.

• Set /etc/hosts file on host machine to include:

  168.33.10 local.topcoder.com
  168.33.10 member.local.topcoder.com
  168.33.10 local.topcoder-dev.com
  168.33.10 member.local.topcoder-dev.com
  168.33.10 local.topcoder-qa.com
  168.33.10 member.local.topcoder-qa.com
  

• Make sure to do a 'git pull' inside the tc-site folder before you get started

• Run 'grunt dev' to build/watch the src folder. This will build the project and configure your local instance against the production database, so please use caution. To use the dev or qa databases, run src/conf/debug-local-dev.sh or src/conf/debug-local-dev.sh

• MacOS Only: If you run grunt dev from your ssh mapped folder, the fuse driver does not always play nice (leaves hidden files that get locked), so it is best to run this from the vagrant machine via vagrant ssh and use the mapped folder just for code modifications.

• The site will be available from any of the above hostnames, but you will want to test using the domain that matches the database instance you have built for to avoid cookie conflicts, etc.

• If you are using the wordpress side:

• The default login/pass for wp-admin is: tcdev/tcdev, no caching is on by default but some js/css changes require you to Update JS/CSS Registry

• You will need to keep wp-config.php up to date with which backend you are using, for instance if you ran sr/conf/debug-local-dev.sh, you would need:

  ne('WP_SITEURL','http://local.topcoder-dev.com');
  ne('WP_HOME','http://local.topcoder-dev.com');