Zen: Building Maintainable Catalyst Applications
by Jay Shirley on Jan 16, 2010
- 2,369 views
After several years of building Catalyst applications, I've established a list of techniques that greatly increase maintainability....
After several years of building Catalyst applications, I've established a list of techniques that greatly increase maintainability.
Subtle points that are easy to understand, and easy to implement, that will help please your users and make your life easier.
Accessibility
Categories
Tags
More...Upload Details
Uploaded via SlideShare as Apple Keynote
Usage Rights
© All Rights Reserved
Statistics
- Favorites
- 3
- Downloads
- 21
- Comments
- 0
- Embed Views
- Views on SlideShare
- 2,337
- Total Views
- 2,369
This means an error action that is verbose, looks at the action that went wrong and is helpful.
Sometimes I send email (using Catalyst::View::Email) or sometimes I just use Catalyst::Log::Log4perl and dispatch FATALs that way.
It’s the developers fault. Your error should explain what information is relevant, and if it can do that, just go ahead and send that on to the developers. Expecting the user to do it just means you’re lazy. So don’t be lazy, and if you want to be lazy, go hack on Rails.
This is an undocumented “private” method because it deviates from the standard logging methods above, but Catalyst::Log and Catalyst::Log::Log4perl both support it. It emits the message as an info message.
If you use external FastCGI, local::lib, you can run and deploy your entire application without ever touching the root account.
This is particularly useful for doing smoke testing, if you have multiple environments.