| # This custom matcher can be used to test state machine | |
| # | |
| # Examples | |
| # | |
| # it { should have_event(:status, :event_name, [:state1, :state2] => [:state3, :state4]) } | |
| # it { should have_event(:status, :event_name, { | |
| # :state1 => :state3, | |
| # :state1 => :state4, | |
| # :state3 => :state3, | |
| # :state2 => :state4 |
| require 'yaml' | |
| desc 'Generates database.yml, optional arguments: [adapter, user, password]' | |
| task :dbconfig => 'database.yml' | |
| file 'database.yml', [:adapter, :username, :password] do |t, args| | |
| Dir.chdir('config') | |
| args.with_defaults(:project_path => Dir.pwd) | |
| DBConfigGenerator.new(t, args).generate | |
| end |
| group :production do | |
| gem 'unicorn' | |
| # Enable gzip compression on heroku, but don't compress images. | |
| gem 'heroku-deflater' | |
| # Heroku injects it if it's not in there already | |
| gem 'rails_12factor' | |
| end |
| # gem 'ckeditor_rails' # from https://github.com/tsechingho/ckeditor-rails | |
| # allow modifying existing template | |
| <textarea name="modified_email" class="ckeditor"> | |
| <%= File.read "#{Rails.root.to_s}/app/views/user_mailer/do_email.html.erb"%> | |
| </textarea> | |
| <%= javascript_include_tag "ckeditor-jquery" %> | |
| <script type="text/javascript"> | |
| $('.ckeditor').ckeditor({ |
| # Basically the nginx configuration I use at konklone.com. | |
| # I check it using https://www.ssllabs.com/ssltest/analyze.html?d=konklone.com | |
| # | |
| # To provide feedback, please tweet at @konklone or email [email protected]. | |
| # Comments on gists don't notify the author. | |
| # | |
| # Thanks to WubTheCaptain (https://wubthecaptain.eu) for his help and ciphersuites. | |
| # Thanks to Ilya Grigorik (https://www.igvita.com) for constant inspiration. | |
| server { |
Prerequisites:
Software components used:
These files work together to extract useful data from a Rails application and publish it through a ZeroMQ PUSH socket as JSON.
The code in application_controller.rb will automatically log every request and exception, but you're free to log other things. If you're inside a controller, you can use log_message(atts) or emit_event(atts). These controller methods simply delegate to the global object $ZMQ_LOGGER, which responds to log(atts) and emit(atts). They add the data.http.request-id key if not already present.
The difference between logging and emitting is somewhat blurry, but I like to think of log messages as something that will be saved somewhere and emitted events as ephemeral.
All attributes are expected to use strings as keys. If you use symbols, you may experience issues.
You may use these files as you wish, with one exception: You may not package them into a reusable library and publish it. This is not easily reusable code, and any attempt to make it into a pre-packaged library will result
| require 'rspec/expectations' | |
| # It would be better if we could change this to pending on the fly, but that happens in a higher scope, | |
| # so there's nothing but "pass" or "fail" | |
| RSpec::Matchers.define :maybe_match do |expected| | |
| match do |actual| | |
| true | |
| end | |
| description do |actual| |
| # coding=UTF-8 | |
| from __future__ import division | |
| import re | |
| # This is a naive text summarization algorithm | |
| # Created by Shlomi Babluki | |
| # April, 2013 | |
| class SummaryTool(object): |
| build_package_combined_patch() { | |
| local package_name="$1" | |
| { | |
| curl https://github.com/funny-falcon/ruby/compare/p385...p385_falcon_gc.diff | patch -p1 | |
| autoconf | |
| ./configure --prefix="$PREFIX_PATH" $CONFIGURE_OPTS | |
| make -j 8 | |
| make install | |
| } >&4 2>&1 |
