Huge update.

Moved all posts from textile to markdown. Updated all the CSS and
styles. Added a new page for the resume.

1 files changed, 0 insertions, 26 deletions

diff --git a/_posts/2009-06-25-how-to-prevent-some-components-to-be-loaded-by-catalyst.textile b/_posts/2009-06-25-how-to-prevent-some-components-to-be-loaded-by-catalyst.textile
deleted file mode 100644
index fefbede..0000000
--- a/_posts/2009-06-25-how-to-prevent-some-components-to-be-loaded-by-catalyst.textile
+++ /dev/null
@@ -1,26 +0,0 @@
----
-layout: post
-category: perl
-title: How to prevent some components to be loaded by Catalyst
----
-
-Let's say you have a "large" [Catalyst](http://search.cpan.org/perldoc?Catalyst) application, with a lot of compoments. When you deploy your application, or when you want to test it while your developping, you may not want to have some of thoses components loaded (you don't have all the dependencies, they are incompatible, etc...). Catalyst use [Module::Pluggable](http://search.cpan.org/perldoc?Module::Pluggable) to load the components, so you can easily configure this. In your application's configuration, add:
-
-{% highlight yaml %}
-setup_components:
-  except:
-    - MyApp::Model::AAAA
-    - MyAPP::Model::BBBB::REST
-    ...
-{% endhighlight %}
-
-Module::Pluggable have some other interesting features. You may have a second Catalyst application, and want to use one or more components from this one. You can easily do this: 
-
-{% highlight yaml %}
-setup_components:
-  search_path:
-    - MyApp
-    - MyOtherApp::Model
-{% endhighlight %}
-
-