Commit 4edefde8 authored by Michael McAndrew's avatar Michael McAndrew

clearer instructions on using www-test

parent 326a0142
#Development workflow
All new code, etc. should be developed locally, commited to this repository, tested on www-test.civicrm.org, and the deployed on production.
All new code, etc. should be developed locally, commited to this repository, tested on www-test.civicrm.org, and the deployed on production. www-test should NOT be used for code based development.
New configurations (i.e. configuration changes made via the UI etc. can/should be made on www-test.civicrm.org first before being deployed on production.
You can use www-test to experiment with ad-hoc configuration changes (e.g. to views, permissions, etc.) but note that many peole have access to www-test, and it gets over written with data from www-prod on a regular basis, e.g. when testing upgrades of CiviCRM. Therefore, you should NOT assume that your config changes will be on www-test next time you look.
All custom modules should be added to the sites/all/modules/custom directory.
**Note:** you should not make UI configuration changes on test that you want to keep as it is getsover written with / synced from prod from time to time.
#Syncing to test and local environments
Syncing to www-test and local development environments is done in the standard way (mysqldump and restore the databases and rsync/copy the files). You should not need to worry about backing up the www-test database because no important data should be stored there (see development workflow above).
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment