This repository has been archived by the owner on Feb 1, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1
/
DEVELOPMENT_README.txt
55 lines (40 loc) · 1.83 KB
/
DEVELOPMENT_README.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
Development using a virtual machine
###################################
You can set up a development virtual machine for ZF1 unit testing and library
development following these simple instructions.
1. Install requirements for VM. (Note: these are not required by ZF1 itself)
- VirtualBox (https://www.virtualbox.org/)
- Ruby (http://www.ruby-lang.org/)
- Vagrant (http://vagrantup.com/)
2. Checkout repository to any location
> svn checkout http://framework.zend.com/svn/framework/standard/trunk zf1-dev
> cd zf1-dev
3. Start the process by running Vagrant.
> vagrant up
This will take a long while as it has to download a VM image and then
provision it. Once it has finished, it will exit and leave you back at the
command prompt.
4. SSH into the VM
> vagrant ssh
5. Build a version of PHP.
> php-build.sh 5.3.11
This also takes a while as it compiles PHP for you!
6. Select PHP to use:
> pe 5.3.11
7. Run tests
> cd /vagrant/tests
> phpunit --stderr -d memory_limit=-1 Zend/Acl/AclTest.php
> phpunit --stderr -d memory_limit=-1 Zend/Amf/AllTests.php
(etc...)
Note that you can repeat items 5 and 6 to create any version if PHP.
Notes:
- The VM will be running in the background as VBoxHeadless
- HTTP and SSH ports on the VM are forwarded to localhost (22 -> 2222, 80 -> 8081)
- The zf1-dev directory you checked out will be mounted inside the VM at /vagrant
- You can develop by editing the files you cloned in the IDE of you choice.
- To stop the VM do one of the following:
> vagrant suspend # if you plan on running it later
> vagrant halt # if you wish to turn off the VM, but keep it around
> vagrant destroy # if you wish to delete the VM completely
- Also, when any of of the Puppet manifests change (.pp files), it is a good idea to rerun them:
> vagrant provision