Cleaning up the git history of a Symfony 2 project.

If your Git repository contains files that should never have been commited, you are in the right place. Let’s say you have [commited a configuration file][github-fails] containing sensitive data such as SSH access to your servers or database credentials. Or you have commited an external library massively increasing the repository size, there is a quite simple way to correct that. You night have noticed that removing the file from git in a commit does not decrease the repository size nor remove the file from the file from history. Indeed, every file that once has been tracked is fully present in the git history since Git is able to fully restore the workspace to a given commit. If the file was present in a commit, Git must have the file stored somewhere.


Test your emails with Behat and Symfony

When writing tests with Behat, one is often confronted with the need to test email sending. For example, when a user registers for your application, the user might need to confirme his email address. In that case an email is send to the user containing a link he has to follow in order to confirm. Actually testing that this email is send is not that complicated with Behat and Symfony.


Insert implementation performance on Mysql

Currently, I am working on a heavy read/write database application in Play (teasing: will be online in a couple of days!) and I was faced with a classic performance dillema. I have a lot of data to insert in my Mysql database but a lot of that data could be a duplicate of data already in the table and in that case, I don’t want it. I was wondering what would be the best implementation for this kind of situation and decided to create a little benchmark.