Skip to content

Instantly share code, notes, and snippets.

@pius
Created October 8, 2008 02:27
Show Gist options
  • Save pius/15432 to your computer and use it in GitHub Desktop.
Save pius/15432 to your computer and use it in GitHub Desktop.
~ Loaded DEVELOPMENT Environment...
~ loading gem 'dm-timestamps' ...
~ loading gem 'dm-types' ...
~ loading gem 'dm-serializer' ...
~ loading gem 'dm-validations' ...
/usr/local/lib/ruby/gems/1.8/gems/merb-core-0.9.8/lib/merb-core/core_ext/kernel.rb:71:in `require': no such file to load -- dm-paperclip (LoadError)
from /usr/local/lib/ruby/gems/1.8/gems/merb-core-0.9.8/lib/merb-core/core_ext/kernel.rb:71:in `load_dependency'
from /usr/local/lib/ruby/gems/1.8/gems/merb-core-0.9.8/lib/merb-core/bootloader.rb:280:in `load_dependencies'
from /usr/local/lib/ruby/gems/1.8/gems/merb-core-0.9.8/lib/merb-core/bootloader.rb:280:in `each'
from /usr/local/lib/ruby/gems/1.8/gems/merb-core-0.9.8/lib/merb-core/bootloader.rb:280:in `load_dependencies'
from /usr/local/lib/ruby/gems/1.8/gems/merb-core-0.9.8/lib/merb-core/bootloader.rb:275:in `run'
from /usr/local/lib/ruby/gems/1.8/gems/merb-core-0.9.8/lib/merb-core/bootloader.rb:70:in `run'
from /usr/local/lib/ruby/gems/1.8/gems/merb-core-0.9.8/lib/merb-core/server.rb:149:in `bootup'
from /usr/local/lib/ruby/gems/1.8/gems/merb-core-0.9.8/lib/merb-core/server.rb:40:in `start'
from /usr/local/lib/ruby/gems/1.8/gems/merb-core-0.9.8/lib/merb-core.rb:114:in `start'
from /usr/local/lib/ruby/gems/1.8/gems/merb-core-0.9.8/bin/merb:11
from /usr/local/bin/merb:19:
$KCODE = 'UTF8'
#
# ==== Structure of Merb initializer
#
# 1. Load paths.
# 2. Dependencies configuration.
# 3. Libraries (ORM, testing tool, etc) you use.
# 4. Application-specific configuration.
#
# ==== Set up load paths
#
# Add the app's "gems" directory to the gem load path.
# Note that the gems directory must mirror the structure RubyGems uses for
# directories under which gems are kept.
#
# To conveniently set it up, use gem install -i <merb_app_root/gems>
# when installing gems. This will set up the structure under /gems
# automagically.
#
# An example:
#
# You want to bundle ActiveRecord and ActiveSupport with your Merb
# application to be deployment environment independent. To do so,
# install gems into merb_app_root/gems directory like this:
#
# gem install -i merb_app_root/gems activesupport-post-2.0.2.gem activerecord-post-2.0.2.gem
#
# Since RubyGems will search merb_app_root/gems for dependencies, order
# in the statement above is important: we need to install ActiveSupport which
# ActiveRecord depends on first.
#
# Remember that bundling of dependencies as gems with your application
# makes it independent of the environment it runs in and is a very
# good, encouraged practice to follow.
# If you want modules and classes from libraries organized like
# merbapp/lib/magicwand/lib/magicwand.rb to autoload,
# uncomment this.
#Merb.push_path(:lib, Merb.root / "lib") # uses **/*.rb as path glob.
# add 'lib' folder to path
Merb.push_path(:lib, File.join(File.dirname(__FILE__), "..", "lib"))
# ==== Dependencies
# dm-more dependencies
dependency 'dm-timestamps'
dependency 'dm-types'
dependency 'dm-serializer'
dependency 'dm-validations'
dependency 'dm-paperclip'
# merb-more dependencies
dependency 'merb-action-args'
dependency 'merb-assets'
dependency 'merb-builder'
dependency 'merb-cache'
dependency 'merb-haml'
dependency 'merb-jquery'
dependency 'merb-mailer'
dependency 'merb-slices'
# merb-plugins dependencies
dependency 'merb-helpers'
dependency 'merb_param_protection'
# merb_auth dependencies
dependency "merb_auth-core"
dependency "merb_auth-more"
dependency "merb_auth_password_slice"
# These are a few, but not all, of the standard merb-more dependencies:
#
# dependency "merb-action-args" # Provides support for querystring arguments to be passed in to controller actions
# dependency "merb-assets" # Provides link_to, asset_path, auto_link, image_tag methods (and lots more)
# dependency "merb-cache" # Provides your application with caching functions
# dependency "merb-haml" # Adds rake tasks and the haml generators to your merb app
# dependency "merb-jquery" # Provides a #jquery method to insert jQuery code in to a content block
# dependency "merb-mailer" # Integrates mail support via Merb Mailer
# These are a few, but not all, of the merb-plugin dependencies:
#
# dependency "merb_helpers" # Provides the form, date/time, and other helpers
# dependency "merb_param_protection" # Lets you have better control over your query string params and param logging
# dependency "merb_stories" # Provides rspec helper methods for your application
# Miscellaneous dependencies:
#
# Specify more than one dependency at a time with the #dependencies method:
# dependencies "RedCloth", "BlueCloth"
# Specify a specific version of a dependency
# dependency "RedCloth", "> 3.0"
# Specify more than one dependency at a time as well as the version:
# dependencies "RedCloth" => "> 3.0", "BlueCloth" => "= 1.0.0"
# You can also add in dependencies after your application loads.
Merb::BootLoader.after_app_loads do
# For example, the magic_admin gem uses the app's model classes. This requires that the models be
# loaded already. So, we can put the magic_admin dependency here:
# dependency "magic_admin"
#Merb::Slices::config[:merb_auth][:layout] = :application
DataMapper.auto_upgrade!
end
#
# ==== Set up your ORM of choice
#
# Merb doesn't come with database support by default. You need
# an ORM plugin. Install one, and uncomment one of the following lines,
# if you need a database.
# Uncomment for DataMapper ORM
use_orm :datamapper
# Uncomment for ActiveRecord ORM
# use_orm :activerecord
# Uncomment for Sequel ORM
# use_orm :sequel
#
# ==== Pick what you test with
#
# This defines which test framework the generators will use.
# RSpec is turned on by default.
#
# To use Test::Unit, you need to install the merb_test_unit gem.
# To use RSpec, you don't have to install any additional gems, since
# merb-core provides support for RSpec.
#
# use_test :test_unit
use_test :rspec
#
# ==== Choose which template engine to use by default
#
# Merb can generate views for different template engines, choose your favourite as the default.
# use_template_engine :erb
use_template_engine :haml
#
# ==== Set up your basic configuration
#
# IMPORTANT:
#
# early on Merb boot init file is not yet loaded.
# Thus setting PORT, PID FILE and ADAPTER using init file does not
# make sense and only can lead to confusion because default settings
# will be used instead.
#
# Please use command line options for them.
# See http://wiki.merbivore.com/pages/merb-core-boot-process
# if you want to know more.
Merb::Config.use do |c|
# Sets up a custom session id key which is used for the session persistence
# cookie name. If not specified, defaults to '_session_id'.
# c[:session_id_key] = '_session_id'
# The session_secret_key is only required for the cookie session store.
c[:session_secret_key] = '352e5bed8634fdbf0d15d0c505b8ff594aebb829'
# There are various options here, by default Merb comes with 'cookie',
# 'memory', 'memcache' or 'container'.
# You can of course use your favorite ORM instead:
# 'datamapper', 'sequel' or 'activerecord'.
c[:session_store] = 'cookie'
c[:use_mutex] = false
end
# ==== Tune your inflector
# To fine tune your inflector use the word, singular_word and plural_word
# methods of English::Inflect module metaclass.
#
# Here we define erratum/errata exception case:
#
# English::Inflect.word "erratum", "errata"
#
# In case singular and plural forms are the same omit
# second argument on call:
#
# English::Inflect.word 'information'
#
# You can also define general, singularization and pluralization
# rules:
#
# Once the following rule is defined:
# English::Inflect.rule 'y', 'ies'
#
# You can see the following results:
# irb> "fly".plural
# => flies
# irb> "cry".plural
# => cries
#
# Example for singularization rule:
#
# English::Inflect.singular_rule 'o', 'oes'
#
# Works like this:
# irb> "heroes".singular
# => hero
#
# Example of pluralization rule:
# English::Inflect.singular_rule 'fe', 'ves'
#
# And the result is:
# irb> "wife".plural
# => wives
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment