| #!/usr/bin/env ruby | |
| require 'time' | |
| require 'logger' | |
| require 'aws-sdk' | |
| AWS_REGION = "us-east-1" | |
| AWS_KEY_ID = "" | |
| AWS_SECRET_KEY = "" |
| $ sudo su - | |
| # mkdir /etc/resolver | |
| # cat > /etc/resolver/test | |
| nameserver 127.0.0.1 | |
| port 2155 | |
| ^D | |
| ^D | |
| $ brew install dnsmasq | |
| $ dnsmasq --port=2155 --no-resolv --address=/.test/127.0.0.1 | |
| $ ping foo.test |
| class Counter | |
| include Sidekiq::Worker | |
| # I'd use a separate Redis instance from Sidekiq | |
| REDIS = ConnectionPool.new(size: 5) { Redis.new(...) } | |
| # Call this API in your Rails app code to increment counters | |
| # as the user does things. | |
| def self.incr(name, amount=1) | |
| key = "counter-#{name}-#{current_window}" |
| require 'rubygems' | |
| require 'eventmachine' | |
| require 'em-websocket' | |
| require 'json' | |
| class Connection | |
| attr_accessor :socket, :user_id | |
| def initialize(socket, user_id) | |
| @socket = socket |
| #!/usr/bin/env ruby | |
| require 'rubygems' | |
| require 'bundler' | |
| require 'fileutils' | |
| require 'net/http' | |
| require 'net/https' | |
| require 'uri' | |
| TMP_DIR = "/tmp/gems" |
| #!/bin/bash | |
| ##### | |
| # Builds a custom nginx | |
| # | |
| # RELEASE_TAGS="+your+tags+here" | |
| # RELEASE_MAINTAINER="Your Name Here" | |
| # RELEASE_MAINTAINER_EMAIL="hi@example.com" | |
| # RELEASE_MESSAGE="Some message" | |
| # |
| BEGIN { | |
| require 'net/http' | |
| Net::HTTP.module_eval do | |
| alias_method '__initialize__', 'initialize' | |
| def initialize(*args,&block) | |
| __initialize__(*args, &block) |
| class ApplicationController < ActionController::Base | |
| before_filter :ensure_xhr | |
| private | |
| def ensure_xhr | |
| if request.get? && request.format && (request.format.js? || request.format.json?) | |
| head :forbidden unless request.xhr? | |
| end | |
| end | |
| end |
This configuration works with Upstart on Ubuntu 12.04 LTS
The reason why it needs to be done this way (i.e. with the pre-start and post-stop stanzas), is because Upstart
is unable to track whever Unicorn master process re-execs itself on hot deploys. One can use it without hot-deploys
and run Unicorn in foreground also, it then only needs one exec stanza.
This presumes you are not using RVM, so no voodoo dances.
These are my notes from deploying a boilerplate Rails app to AWS Lambda (yeah, you read that right) using Lamby. Basically this is me going through the Quick Start guide.
Questions/comments: https://twitter.com/heyjoshwood