Working With Multiple Sandboxes: Difference between revisions

From VrlWiki
Jump to navigation Jump to search
New page: You might want to develop code in more than one sandbox. This is particularly useful for testing in a separate sandbox from your development sandbox. Note that you do not need multiple s...
 
No edit summary
Line 1: Line 1:
You might want to develop code in more than one sandbox.  This is particularly useful for testing in a separate sandbox from your development sandbox.
You might want to develop code in more than one sandbox.  This is particularly useful for testing in a separate sandbox from your development sandbox.


Note that you do not need multiple sandboxes to work on multiple versions of a project.  Program development directories (under <code>project/</code> and <code>common/</code>) can be located anywhere and there can have replicated variations.  In this case the variants all share the same <code>install/</code> and <code>import/</code> directories.
Note that you do not need multiple sandboxes to work on multiple versions of a project.  Program development directories (under '''project/''' and '''common/''') can be located anywhere and there can have replicated variations.  In this case the variants all share the same '''install/''' and '''import/''' directories.
 
* Setting up and additional sandbox.
 
 
* Working with the legacy build system.

Revision as of 16:43, 21 July 2010

You might want to develop code in more than one sandbox. This is particularly useful for testing in a separate sandbox from your development sandbox.

Note that you do not need multiple sandboxes to work on multiple versions of a project. Program development directories (under project/ and common/) can be located anywhere and there can have replicated variations. In this case the variants all share the same install/ and import/ directories.

  • Setting up and additional sandbox.


  • Working with the legacy build system.