Comments on: Quick Symfony Trick – The power of filters http://www.mellowmorning.com/2007/09/22/quick-symfony-trick-the-power-of-filters/ Blogging the world of IT and Business Sun, 29 Jan 2012 20:03:56 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: tomasz ducin http://www.mellowmorning.com/2007/09/22/quick-symfony-trick-the-power-of-filters/comment-page-1/#comment-8050 tomasz ducin Sat, 15 May 2010 11:29:42 +0000 http://www.mellowmorning.com/2007/09/22/quick-symfony-trick-the-power-of-filters/#comment-8050 You can see how to use advanced admin filters in new symfony 1.3-1.4 releases at http://symfony-world.blogspot.com/2010/01/custom-admin-generator-filter-example.html You can see how to use advanced admin filters in new symfony 1.3-1.4 releases at http://symfony-world.blogspot.com/2010/01/custom-admin-generator-filter-example.html

]]> By: My Hobby is Programming » Blog Archive » Quick Symfony Trick - The power of filters http://www.mellowmorning.com/2007/09/22/quick-symfony-trick-the-power-of-filters/comment-page-1/#comment-373 My Hobby is Programming » Blog Archive » Quick Symfony Trick - The power of filters Tue, 30 Oct 2007 11:24:39 +0000 http://www.mellowmorning.com/2007/09/22/quick-symfony-trick-the-power-of-filters/#comment-373 [...] read more | digg story [...] [...] read more | digg story [...]

]]> By: Simon http://www.mellowmorning.com/2007/09/22/quick-symfony-trick-the-power-of-filters/comment-page-1/#comment-270 Simon Fri, 12 Oct 2007 09:57:59 +0000 http://www.mellowmorning.com/2007/09/22/quick-symfony-trick-the-power-of-filters/#comment-270 you could also define some settings in the settings file, and use symfony's already defined production / test / development settings, by defining which index it hits.. Thats similar, but doesn't require you to create another filter, which has to be pre-processed.. you could also define some settings in the settings file, and use symfony’s already defined production / test / development settings, by defining which index it hits..

Thats similar, but doesn’t require you to create another filter, which has to be pre-processed..

]]> By: Lukas http://www.mellowmorning.com/2007/09/22/quick-symfony-trick-the-power-of-filters/comment-page-1/#comment-192 Lukas Thu, 04 Oct 2007 08:53:14 +0000 http://www.mellowmorning.com/2007/09/22/quick-symfony-trick-the-power-of-filters/#comment-192 Yeah, different env's are not what you want. Env's are for separating if I want a debug toolbar to show up or not. But for preproduction testing (or deploying on multiple servers in a cluster), its not feasible to have a dev and prod config for all permutations. The solution I found is the following: - On all but the most default dev setup, I need to place a file with a unique identifier for the server (or application setup) in a file in the root dir of the symfony app - This file is read inside the index.php (frontend_dev.php etc) and is put into a constant - Now inside my yml files I simply add some PHP code that checks this constant and echo's the proper setting out in the yml file This approach as the advantage of leverging the yml file cache instead of adding another filter, which is a significant overhead. In theory I could also cache the contents of the file that identifies the application setup. I guess I could also put something into the .htaccess file or the vhost setting Yeah, different env’s are not what you want. Env’s are for separating if I want a debug toolbar to show up or not. But for preproduction testing (or deploying on multiple servers in a cluster), its not feasible to have a dev and prod config for all permutations.

The solution I found is the following:
- On all but the most default dev setup, I need to place a file with a unique identifier for the server (or application setup) in a file in the root dir of the symfony app
- This file is read inside the index.php (frontend_dev.php etc) and is put into a constant
- Now inside my yml files I simply add some PHP code that checks this constant and echo’s the proper setting out in the yml file

This approach as the advantage of leverging the yml file cache instead of adding another filter, which is a significant overhead. In theory I could also cache the contents of the file that identifies the application setup. I guess I could also put something into the .htaccess file or the vhost setting

]]> By: vbali blogja »  links for 2007-09-29 http://www.mellowmorning.com/2007/09/22/quick-symfony-trick-the-power-of-filters/comment-page-1/#comment-142 vbali blogja »  links for 2007-09-29 Sat, 29 Sep 2007 22:21:14 +0000 http://www.mellowmorning.com/2007/09/22/quick-symfony-trick-the-power-of-filters/#comment-142 [...] Quick Symfony Trick - The power of filters Eltér? konfigurációs beállítások alkalmazása különböz? szerverekhez symfony flterrel. (tags: symfony framework development php webdev) Oszd meg ezt a bejegyzést : Ezek az ikonok ún. közösségi könyvjelz? oldalakra mutatnak, ahol meg lehet osztani másokkal is amit fontosnak találsz. [...] [...] Quick Symfony Trick – The power of filters Eltér? konfigurációs beállítások alkalmazása különböz? szerverekhez symfony flterrel. (tags: symfony framework development php webdev) Oszd meg ezt a bejegyzést : Ezek az ikonok ún. közösségi könyvjelz? oldalakra mutatnak, ahol meg lehet osztani másokkal is amit fontosnak találsz. [...]

]]> By: tschellenbach http://www.mellowmorning.com/2007/09/22/quick-symfony-trick-the-power-of-filters/comment-page-1/#comment-88 tschellenbach Mon, 24 Sep 2007 19:24:18 +0000 http://www.mellowmorning.com/2007/09/22/quick-symfony-trick-the-power-of-filters/#comment-88 In most cases that is also a viable solution, however that approach - forces you to have a duplicate settings specification for two environments ( I am unsure how much of an issue this becomes with larger configs ) - requires more duplication if you would like to have access to multiple environments on your live server. For me the above approach become more attractive because i also wanted to define constants in a filter, so the effort was about the same. In most cases that is also a viable solution, however that approach

- forces you to have a duplicate settings specification for two environments ( I am unsure how much of an issue this becomes with larger configs )

- requires more duplication if you would like to have access to multiple environments on your live server.

For me the above approach become more attractive because i also wanted to define constants in a filter, so the effort was about the same.

]]> By: hardrock http://www.mellowmorning.com/2007/09/22/quick-symfony-trick-the-power-of-filters/comment-page-1/#comment-87 hardrock Mon, 24 Sep 2007 18:26:20 +0000 http://www.mellowmorning.com/2007/09/22/quick-symfony-trick-the-power-of-filters/#comment-87 Why not use two different environments? I'm using the environments 'live' and 'prod' here, sharing all except connection specific settings. Regards Why not use two different environments? I’m using the environments ‘live’ and ‘prod’ here, sharing all except connection specific settings.

Regards

]]> By: Jo http://www.mellowmorning.com/2007/09/22/quick-symfony-trick-the-power-of-filters/comment-page-1/#comment-85 Jo Mon, 24 Sep 2007 14:45:53 +0000 http://www.mellowmorning.com/2007/09/22/quick-symfony-trick-the-power-of-filters/#comment-85 this is what I was looking for. Thanks jo this is what I was looking for.

Thanks

jo

]]> By: rpsblog.com » A week of symfony #38 (17->23 September 2007) http://www.mellowmorning.com/2007/09/22/quick-symfony-trick-the-power-of-filters/comment-page-1/#comment-82 rpsblog.com » A week of symfony #38 (17->23 September 2007) Sun, 23 Sep 2007 21:38:48 +0000 http://www.mellowmorning.com/2007/09/22/quick-symfony-trick-the-power-of-filters/#comment-82 [...] Quick Symfony Trick - The power of filters [...] [...] Quick Symfony Trick – The power of filters [...]

]]>