Posts Tagged ‘logging’

Release 0.8.0

Monday, October 6th, 2008

Here it is the 0.8.0 release of Mack! What a fun and exciting release it is as well. There are a few big changes under the hood, all for the better of course, but there’s only really one that will cause existing Mack projects some conversion pain. However, we’ve tried to take the sting out of that with a helpful rake task.

Configatron Support

Mack 0.8.0 replaces the old application_configuration system with the new ultra sexy and cool, Configatron system. This is a much better way of doing system configurations, and I’m sure you’ll agree once you give it a spin. We’ve tried to take the edge off the conversion of these configuration systems with a helpful little rake task:

$ rake mack:update:configuration

For most cases, that task should do just fine. There might be a few places you have to tweak, such as in your own code, but once you do that, you’ll love Configatron!

For more information about using Configatron checkout this page:

http://www.mackery.com/configuration/configatron

A New Router

That’s right, the router in Mack has been completely rewritten from the ground up, yet unlike other frameworks, we’ve managed to keep our external API the same, so you don’t have to change your routes.rb at all. :) That’s a bit of good news, isn’t it?

What do you get with the new router? Well, for one, it should be faster, that’s always a plus. You can also now do ‘wildcard’ parameters in routes, use procs, extended ‘resourced’ routes, define ‘host’ and ‘scheme’ parameters, use regular expressions, and a few other little nifty things. Plus, because of the rewrite, it’s going to make it easier to extending the routing system to be even more powerful! In a future release, sometime in the 0.8.x series, you’ll even be able to plugin in your own router just by implementing a few API methods.

For more information about the new router, and what you can do, check out:

http://www.mackery.com/routing/index

Asset Management

There is now a really great asset management system that easily allows you to build bundles of CSS and JavaScript files to help keep your code neat and easy to use. Bundle that with the new mack-asset_packager gem, and support for asset hosts, you get a simple, easy, and fast way to compress and deliver your assets. 

For more information, checkout these helpful pages from the user guide:

http://www.mackery.com/views/asset_mgr
http://www.mackery.com/views/asset_host 

Misc.

As always, there’s a bunch of other great stuff just lurking around in this release. A better logger, for a start, more helpers, bug fixes, better error reporting, default 404 and 500 pages, and more. Please download and enjoy the release, I’m sure you’ll find worth it. Enjoy!

Changelog:

  1. [#187] Fixed: When an exception is raised, the request doesn’t get ‘logged’
  2. [#185] Fixed: .html is being appended to logged requests when there’s a 404
  3. [#184] Request logging should also print the message of the status code
  4. [#183] Updates to asset mgr/host
  5. [#181] Content-type can now be set with calling render.
  6. [#179] When configatron.mack.show_exceptions is false you now either the public/404.html or public/500.html file.
  7. [#178] Added a configure parameter to turn off log coloring
  8. [#176] Added a Google Analytics helper.
  9. [#175] Generating urls should use host or scheme if defined
  10. [#171] Ability to extend resources in routes
  11. [#170] Regex support in routes
  12. [#169] Proc support for Routes
  13. [#168] Fixed ERB errors not being reported correctly.
  14. [#167] Rake task to convert app config yamls to configatron
  15. [#165] Asset Packager
  16. [#164] Response helper for ‘attachments’
  17. [#159] Added link_unless_current and link_if helpers
  18. [#156] Added ‘Wildcard’ Routes support
  19. [#152] INCOMPATIBILITY NOTICE: Removed deprecated support for delivered_emails use delivered_notifiers instead.
  20. [#138] Added support for ‘host’ & ‘scheme’ parameters in routes
  21. [#135] Replaced log4r with logging gem.
  22. [#119] Freeze gems
  23. [#106] INCOMPATIBILITY NOTICE: Removed deprecated support for droute_url
  24. [#93] INCOMPATIBILITY NOTICE: Removed deprecated support for ‘top’ level ApplicationHelper
  25. [#23] INCOMPATIBILITY NOTICE: Removed support for application_configuration and added support for configatron
  26. gem: logging 0.9.4
  27. gem: thin 1.0.0
  28. gem: rspec 1.1.8
  29. gem: configatron 2.1.4
  30. gem: cachetastic 2.0.0

Release 0.6.1.1

Monday, August 4th, 2008

Mack 0.6.1.1 features 38 completed tickets and a whole host of really great features and improvements. Here’s a quick overview of a few of the big features in Mack 0.6.1.1.

Page Caching

There is now a mack-caching gem which gives you easy to use page caching when you require it. To use page caching first you need to add it to your gems.rb file like such:

gem.add "mack-caching", :libs => "mack-caching"

That will require the gem and give your app access to the page caching libraries. Next you to turn on page caching in your application. In the appropriate config/*.yml file add the following:

use_page_caching: true

Now, you just need to tell your controllers which actions they should cache:

class FooController
  include Mack::Controller
  cache_pages :o nly => [:index, :show]
end

If you give the cache_pages no optional parameters then it will cache all the actions for that controller. Alternatively, you could give it an :except parameter to list the actions you don’t want cached. 

Notifiers (aka Mailers)

Mack now has a mack-notifier gem that will be the repository for all ‘notification’ systems, the first of which is email. The Mack::Notifier API is simple and easy to use and will allow developers to plugin in different notification systems under the cover without having to change their application code. 

A notifier can look as simple as:

class WelcomeEmail
  include Mack::Notifier
end

With that you can then write the following bit of code:

we = WelcomeEmail.new
we.to = "foo@example.com"
we.from = "bar@example.com"
we.subject = "Hello World"
we.body(:text) = "My plain text body"
we.body(:html) = "My html body"
we.attach(Mack::Notifier::Attachment.new("/path/to/my/file")) 
we.deliver

Obviously there’s a lot more to the API, including a validations module, but that’s a subject for another post. 

JavaScript (aka RJS)

The mack-javascript gem now gives you Rails-like RJS support for Mack. The default library to use with mack-javascript is jQuery, but there is prototype support available as well. 

Data Factory

Creating faux data for testing can be a real nightmare. Fixtures can be difficult to maintain and trying to create your own faux data can be a chore. That’s where the mack-data_factory gem comes in.

For each model that you want to produce, you will need to define a factory class.  

Let’s say that I have 2 models: Item and User, and Item belongs to user.  So the factories will look like the following:

class ItemFactory
  include Mack::Data::Factory
  field :title, "MyItem"
  field :o wner_id, {:user => 'id'}
end

class UserFactory
  include Mack::Data::Factory
  field :username, "planters", :length => 25, :content => :alpha
  field :password, "roastedPeanuts", :immutable => true
end

So, the 2 classes above defined the factory for item and user.  As you can see, each factory will need to explicitly list all the fields that it will populate, and for each field, you can define rules on how the content is generated.

Supported content types: 

  • :alpha –> alphabets.  rules: [:length, :min_length, :max_length]
  • :alphanumeric –> alphabets and number.  rules: same as :alpha
  • :numeric –> numbers [optional, because if the field's default value is number, its content type will automatically set to numeric)
  • :email --> generate random email address
  • :username --> generate random username
  • :domain --> generate random domain name
  • :firstname --> generate first name
  • :lastname --> generate last name
  • :name --> generate full name
  • :city --> generate city name
  • :streetname --> generate street name
  • :state --> generate state.  rules: [:country --> :us or :uk, :abbr --> true if you want a abbreviated state name (us only)]
  • :zipcode –> generate zipcode. rules: [:country --> :us or :uk]
  • :phone –> generate phone number
  • :company –> generate company name.  rules: [:include_bs --> include sales tag line]
    example:  field, “”, :content => :company, :include_bs => true could generate something like:
    Fadel-Larkin monetize cross-media experiences
There’s a lot more to the mack-data_factory gem, so I highly recommend you check it out.

Changelog:

  • [#60] Fixed Mack executable problem
  • [#59] Fixed gems:* tasks
  • [#57] Moved most files under to lib/mack
  • [#56] mack-more: Added Mack::Utils::RegistryMap
  • [#55] mack-more: mack-facets: Mack::Utils::Registry is now Mack::Utils::RegistryList
  • [#54] Added DataMapper 0.9.3 support
  • [#52] mack-more: mack-[orm] should require mack-[orm].rb using its full path.
  • [#51] Application generator should generate orm support in the right place
  • [#50] Mack will now have 2 environment files: mack_core and mack_app.  Mack.rb will load both files, but it gives other module chance to load just the core files and not the application’s files.
  • [#49] Making sure the orm tasks is available when orm_support is removed from the app_config
  • [#49] mack-active_record:  mack-active_record.rb will require mack-active_record_tasks.rb
  • [#49] mack-data_mapper:  mack-data_mapper.rb will require mack-data_mapper_tasks.rb
  • [#49] Updated warning message if orm is defined in app_config (i.e. user only needs to require mack-[orm_name], instead of both that and mack-[orm_name]_tasks).
  • [#48] rake generator:list now displays the correct names for the generator tasks.
  • [#47] rake gems:* tasks now work, and no longer require mack_ruby_core_extensions
  • [#46] Calling .to_param on nil now raises a NoMethodError exception.
  • [#45] rake stats task now works with Test::Unit::TestCase
  • [#44] Mack::Runner has now been extended to allow for greater extension flexibility.
  • [#43] Added a Mack::Utils::Registry class to allow for easy creation of registries.
  • [#42] Sessions can now be turned off globally using the app_config.mack.use_sessions switch.
  • [#41] Deprecate orm_support.rb
  • [#38] There is now a registry of Controllers that are in the system.
  • [#36] Renamed the initialize method in the Mack::Controller module to configure_controller. This gives
  •   control of the initialize method back to the class.
  • [#34] Mack::l10n now raises exception with a fully qualified name.
  • [#33] mack-active_record now requires ActiveRecord 2.0.2 explicitly, not >=2.0.2
  • [#31] Added support for ruby-debug.
  • [#26] Log Coloring for console output.
  • [#24] Added mack-notifier support.
  • [#18] Added Page caching.
  • [#14] Data Factory
  • [#7] Added support for Extlib::Hook in a few places.
  • [#6] RJS support
  • Added a rake tmp:clear task.
  • gem: application_configuration 1.5.1
  • gem: ruby-debug 0.10.0
  • gem: data_mapper 0.9.3