Sha256: c21a55a0333bd026dc95c62ef352d3bbe4fdc461bd0b3da317745831c41cc86f
Contents?: true
Size: 1.69 KB
Versions: 4
Compression:
Stored size: 1.69 KB
Contents
require 'rubygems' unless defined?(Gem) require 'bundler/setup' Bundler.setup(:default, :development) require 'rake' task :default => :rspec require 'rspec/core/rake_task' RSpec::Core::RakeTask.new(:rspec) do |spec| Bundler.setup(:default, :development, :test) spec.pattern = 'spec/**/*_spec.rb' end desc "Run RSpec with code coverage" task :cov do ENV['CONFIGLIERE_COV'] = "yep" Rake::Task[:rspec].execute end require 'yard' YARD::Rake::YardocTask.new do Bundler.setup(:default, :development, :docs) end require 'jeweler' Jeweler::Tasks.new do |gem| Bundler.setup(:default, :development, :test) gem.name = 'configliere' gem.homepage = 'https://github.com/infochimps-labs/configliere' gem.license = 'Apache 2.0' gem.email = 'coders@infochimps.org' gem.authors = ['Infochimps'] gem.summary = %Q{Wise, discreet configuration management} gem.description = <<-EOF You\'ve got a script. It\'s got some settings. Some settings are for this module, some are for that module. Most of them don\'t change. Except on your laptop, where the paths are different. Or when you're in production mode. Or when you\'re testing from the command line. "" So, Consigliere of mine, I think you should tell your Don what everyone knows. "" -- Don Corleone Configliere manage settings from many sources: static constants, simple config files, environment variables, commandline options, straight ruby. You don't have to predefine anything, but you can ask configliere to type-convert, require, document or password-obscure any of its fields. Modules can define config settings independently of each other and the main program. EOF gem.executables = [] end Jeweler::RubygemsDotOrgTasks.new
Version data entries
4 entries across 4 versions & 1 rubygems
Version | Path |
---|---|
configliere-0.4.18 | Rakefile |
configliere-0.4.17 | Rakefile |
configliere-0.4.16 | Rakefile |
configliere-0.4.14 | Rakefile |