We'll respond shortly.
Much like any good Rails engine, using Style Guide is designed to give you as much flexibility as possible. In its default state, Style Guide renders subdirectories full of partials located under app/views/style-guide.
You might be wondering what to do … Read more
Before we start, the
.gemspec itself only appears once. Here it is, as generated by
bundle init and hand-tweaked for relevance:
lib = File.expand_path("../lib", __FILE__) $LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib) require "your_gem/version" Gem::Specification.new do |s| s.name = "your-gem" s.version = YourGem::VERSION s.authors = ["Your Name"] s.email = ["email@example.com"] s.homepage = "https://github.com/you/should-use-github" s.summary = "Describe this gem like you're talking to me." s.description = "Describe this gem like you're talking to your mom." s.require_paths = ["lib"] s.files = `git ls-files`.split("n") s.test_files = `git ls-files -- spec/*`.split("n") s.add_dependency "hashie", "~> 2.0" s.add_development_dependency "rspec", "~> 2.12" end
But what does all this mean? Moreover, how do all these crazy bits fit together?
There comes a time in every project when the deployment process comes of age, and that development arrives with its own set of Capistrano recipes and Rake tasks. The project I'm on hit that point recently, and one of the neat outcomes of its nascent puberty was a simple Capistrano recipe to send a git changelog to our project mailing list.
Here's what this looks like:
$ cap staging deploy ... stuff happens here ... * executing `sendgrid:notify' Changelog: 04fc6dd adding capistrano deployment messages