Hello! The good news is that we’re almost there. I hope you’ve been able to follow my instructions thus far - believe me, the end result is more than worth it. In this part of the tutorial, we will be dealing with the installation of both PEAR and Symfony, as well as the initial setup of a Symfony project. Go ahead, power up your VM and log into your shell account so we can get things started.

PEAR - Installation

• Type ‘cd /usr/ports/devel/pear/‘ and hit Enter
• Type ‘make install clean‘ and hit Enter
• After installation has concluded, log out/in to see the PEAR binary in your path
• Type ‘pear channel-update pear.php.net‘ and hit Enter
• Type ‘pear upgrade-all‘ and hit Enter

Symfony is installed the same way as a regular PEAR package. Easy peasy!

Symfony - Installation

• Type ‘pear channel-discover pear.symfony-project.com‘ and hit Enter
• Type ‘pear install symfony/symfony‘ and hit Enter
• Log out and in to see the Symfony binary in your path

Symfony - Project Setup

• Type ‘mkdir /var/websites/yourdomain.com/www‘ and hit Enter
• Type ‘cd /var/websites/yourdomain.com/www‘ and hit Enter
• Type ‘symfony init-project www‘ and hit Enter
• Type ‘symfony init-app frontend‘ and hit Enter
• Type ‘symfony init-app backend‘ and hit Enter
• Type ‘symfony init-module frontend home‘ and hit Enter
• Fire up your host O/S’s web browser and navigate to your VM’s IP
• If you see a Symfony default success page, you’re done!

Congrats! You now have a virtualised web development platform! There’s not much else to say, really, although I will be covering the installation and configuration of additional tools that will further enhance your development experience. As far as your brand-new Symfony project is concerned, I’ll stop there and leave the rest to the framework’s superb documentation.

1. excessivedemon Says:
   May 13th, 2008 at 1:19 am

   I really like this series. Please, I can’t wait for the next parts (re: installation and configuration of additional tools that will further enhance development experience) =) Looking forward to reading it in the next couple of days. Thanks for these articles, I find them really helpful. =)

2. halfer Says:
   May 13th, 2008 at 11:43 am

   Heh heh - well superhaggis, you’ve got your orders. Hurry up ;o)

3. superhaggis Says:
   May 13th, 2008 at 12:55 pm

   I’ll make time tonight to write the next installment!

4. excessivedemon Says:
   May 16th, 2008 at 1:44 am

   any updates on the “next installment”? can’t wait for setting up SVN and trac and stuff. can’t wait for the rest of the best practices stuff too.

5. neonard0 Says:
   May 16th, 2008 at 6:05 am

   Hi once again, I totally agree with the other comments. I cant way to the next part, literally…’cause I had to install svn, and configure it with apache for some urgent job. I hope I installed it the best way.

   But I promise not to go further Teacher XD

6. rpsblog.com » A week of symfony #71 (5->11 may 2008) Says:
   June 9th, 2008 at 2:39 pm

   [...] Virtualisation: A Symfony Developer’s Best Friend - Part 5 [...]

7. seth pearlberg Says:
   June 23rd, 2008 at 5:58 pm

   Has anyone seen VW cause a huge performance hit … We have seen large spikes in load… yet low I/O, low file swapping and CPU idle time at 90%…

   Any thoughts?

8. superhaggis Says:
   July 27th, 2008 at 9:24 am

   The only issue I’ve had with my own FreeBSD VMs is the guest system time going out of sync with the host system time. This is a TSC issue though, which is something one just has to live with on AMD dual-core hardware.