1. Checkout code from SVN into your ~/Sites folder. From the command line do:

svn co [path to repository] ~/Sites/[projectname] --username [username]

After the checkout, go into your new [projectname] directory and do a fix permissions:

./symfony fix-perms

2. Create a new virtual host in apache. You can skip this step but I find it makes things easier. My entry in my apache .conf file (on my mac its located at /etc/apache2/users/[username].conf where [username] is the username on my mac) looks like this:

<VirtualHost *:80>
	ServerName [projectname].local
	DocumentRoot /Users/[myusername]/Sites/[projectname]/web
</VirtualHost>

I also have add this new domain to my local hosts file at /etc/hosts:

127.0.0.1   [projectname].local

then i restart my webserver with a “sudo apachectl graceful”.

3. set up your local database. On my mac I use Sequel Pro to create the database. I run a..

./symfony propel-build-all

..to regenerate the sql and base model classes. Often I don’t like to commit auto-generated code to svn but rather just the source files from which the new code is generated (you can read the side bar “Best Practice: Checkin all the canonical stuff, and nothing else” with one view on this at http://www.ericsink.com/scm/scm_repositories.html).

Once that is done, normally I would insert the db schema into my new database, like this:

mysql -u root [dbname] < data/sql/lib.model.schema.sql

… but sometimes I want to use a lot of the same basic data from before, so I insert database dump that has actual content:

mysql -u root [dbname] < data/sql/latest.sql

4. configure the symfony project to use your new db. You’ll have to copy the config/databases.yml-dist to database.yml and add your own settings there. The databases.yml file is ignored in our repository, so that way the devs can keep different local configuration settings for our dev environment without having to create lots of different symfony environments (usually I keep them to just dev, stage, production) in the project.

5. load up http://[projectname].local/frontend_dev.php to see if things are working!

The command to view all svn:ignore properties in an entire repository is:

svn propget -R svn:ignore .

Here is the link to my question on SO: How do I view all ignored patterns set with svn:ignore recursively in an svn repository? – Stack Overflow.

Springloops has a feature that will automatically copy your latest code to a server you specify, either automatically with every commit, or manually whenever you need it. Immediately I ran into a problem: Springloops will not fetch any code in an external repository and copy it to your server. This means that when we tried to auto-deploy our little app, all of the symfony files were missing!

Here is what their support (which was speedy, I might add, even for a free account like ours) says:

Unfortunately deploying externals is not supported at the moment. The reason is it slows down the entire process because our engine would have to download changelog and file contents from remote servers. We are working on a solution to speed it up, but for now you will have to upload it manually just like you said. You might consider using svn export rather than checkout to avoid placing “.svn” control directories on your server.

Good to know. So, given that information, here is a list of possible ways to easily deploy changes to your project:

• Use rsync. With symfony this is easy with the “project-deploy” command line tool. This is my preferred method because it’s just so darn easy, and lets me get away upload changes that aren’t yet committed to svn (gasp).
• Checkout a version of your project from SVN on your server. When it comes time to upgrade, do an “svn up” or “svn switch” to get the latest changes or switch to another tagged release.
• Do an svn export as suggested by the support guy to avoid placing the “.svn” directories on the server. If you don’t prevent access to these directories on your web server, it can pose a serious risk.

Subversion With Mac OS X Tutorial.

find . -type d -name .svn -exec rm -rf {} \;

Update 1: Thanks to Jon for this improved method!

Update 2: I have this in my notes too, but I don’t know enough about the shell to know which is better.

find . -iname '.svn' -print0 | xargs -0 rm -rf

Using Common Use-Cases as a reference, this is what I did:

From within my branch:

svn log

This displays the revision number for when my branch was created:

------------------------------------------------------------------------
r23 | stereosv | 2009-02-17 11:42:28 -0500 (Tue, 17 Feb 2009) | 1 line
 
creating branch for xyz

Now I need to find out what revision number the trunk is at. Perfoming an “svn update” within the trunk shows me what version it’s at.

> svn update
At revision 25.

In my case the trunk is at revision 25… implying there were only two commits since the time I checked out my branch. Nice.

Now, it’s time to carry merge these changes into my branch. Back in my branch directory, it’s time to put these revision numbers to good use.

svn merge -r 23:25 svn+ssh://username@svnserver/home/username/svn/project/trunk

What this does is merge the changes that were made between revision 23 (when I created my branch) and revision 25 (the most recent revision of the trunk) in the trunk into my working copy.

Now, it’s time to check in my branch, with the updated changes from the trunk.

svn ci -m "Merged trunk changes r23:25 into my branch"

SVN 1.5 has made some improvements to the way merging works.. So check your SVN version with “svn –version” to make sure you are using the right syntax for your version.

export SVN_SSH="ssh -p xxxx"

where xxxx is the port number. That works well if all of your SVN repositories that you access via SSH use the same port number, and if you *don’t* use svnX.

svnX doesn’t use your .bash_login environment variables before running it’s commands, so it’s doesn’t see you want to use a non-standard ssh. However, you *can* add custom ssh hostnames that use your non standard port, and then pass these to svnX as the path.

Open up ~/.ssh/config (or create it if it doesn’t exist) and add a host name like so:

host svn1
  Hostname svn.yourdomain.com
  Port xxxx
  ForwardAgent no
  ForwardX11 no

And then finally, when you put in the path in svnx, use “svn1″ as the hostname:

Path: svn+ssh://username@svn1/path/to/repository

svnX will now be able to access your svn repository through a non-standard ssh port.

Make the repository

Substitute REPOSNAME with the name of your repository (aka the project name).

$ sudo mkdir /usr/local/svn
$ sudo mkdir /usr/local/REPOSNAME
$ sudo svnadmin create /usr/local/svn/REPOSNAME
$ sudo chown -R www:www /usr/local/svn/REPOSNAME

Configure Apache

I used textmate to edit a new text file named svn.conf, you can use vi or whatever you want.

$ cd /etc/apache2/other
$ mate svn.conf

Inside /etc/apache2/other/svn.conf:

LoadModule dav_svn_module /usr/libexec/apache2/mod_dav_svn.so
<Location /svn>
  DAV svn
  SVNParentPath /usr/local/svn
</Location>

And now restart apache…

$ sudo apachectl graceful

Finally, check out your repository to make sure it worked: http://localhost/svn/REPOSNAME.

Final notes

You may want to secure access to your repository through a password file. In a nutshell, you can use something like sudo htpasswd -cm /etc/apache2/auth/svn USERNAME (you can create this file anywhere but I like to keep all my auth files in a custom “auth” directory). Then edit your svn.conf file and add these lines right before the closing ‘Location’ tag:

Inside /etc/apache2/other/svn.conf:

AuthType Basic
AuthName "SVN"
AuthUserFile /etc/apache2/auth/svn
Require valid-user

If you need more detailed instructions you should head over here.

svn export file:///path/to/your/repository my_export

If you want to zip this baby up:

zip -r my_export.zip my_export

If you wanted to get really creative, and tag this export as a release, you could something like this:

svn copy file:///path/to/repos/trunk file:///path/to/repos/tags/1.0release -m "tagging version 1.0 release"
svn export file:///path/to/repos/tags/1.0release 1.0release
# for a zip:
zip -r 1.0release.zip 1.0release/
# for a tgz
tar -czvf 1.0release.tgz 1.0release.zip/*

References:

• http://svnbook.red-bean.com/en/1.1/re10.html