robocall 0.0.1

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 5f6349a07831bbdcded5479ffd91fa2b071dfc55
+  data.tar.gz: c1fd906aa985e033a2dcc84f420256bf6fa067ab
+SHA512:
+  metadata.gz: 9cbf99e5fac4dd4a523b3cd10835ed75e2b0545078c3bfe673e26aca9b52de375b3506cf86b3114ccd4449bbb8aa4ade8c5f5fd827a31d47659ad138f5d28ca8
+  data.tar.gz: 804e43f82b5b7f2bebcad8a25d3e3252c6ad215a6bb7970272bbae44ed2d2c45503926c8d3237975c1acd86c0564e4af0df79da019bfc54718522dad52377926

data/MIT-LICENSE

@@ -0,0 +1,20 @@
+Copyright 2013 YOURNAME
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.md

@@ -0,0 +1,26 @@
+## About
+
+A rails gem to easily add sending synthesized messages from Rails to any phone number. 
+
+## Install
+
+Add the robocall gem to your Gemfile:
+``` ruby
+gem 'robocall'
+```
+
+Update your bundle and run the migrations from the command line:
+``` shell
+bundle install
+rake robocall:install:migrations
+rake db:migrate
+```
+
+In conf/environment.rb, add the configuration:
+``` ruby
+Robocall.from_phone_number = '555-555-5555'
+Robocall.sid               = 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'
+Robocall.auth_token        = 'yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy'
+```
+
+

data/Rakefile

@@ -0,0 +1,37 @@
+#!/usr/bin/env rake
+begin
+  require 'bundler/setup'
+rescue LoadError
+  puts 'You must `gem install bundler` and `bundle install` to run rake tasks'
+end
+begin
+  require 'rdoc/task'
+rescue LoadError
+  require 'rdoc/rdoc'
+  require 'rake/rdoctask'
+  RDoc::Task = Rake::RDocTask
+end
+
+RDoc::Task.new(:rdoc) do |rdoc|
+  rdoc.rdoc_dir = 'rdoc'
+  rdoc.title    = 'Robocall'
+  rdoc.options << '--line-numbers'
+  rdoc.rdoc_files.include('README.md')
+  rdoc.rdoc_files.include('lib/**/*.rb')
+end
+
+APP_RAKEFILE = File.expand_path("../spec/dummy/Rakefile", __FILE__)
+load 'rails/tasks/engine.rake'
+
+Bundler::GemHelper.install_tasks
+
+Dir[File.join(File.dirname(__FILE__), 'tasks/**/*.rake')].each {|f| load f }
+
+require 'rspec/core'
+require 'rspec/core/rake_task'
+
+
+desc "Run all specs in spec directory (excluding plugin specs)"
+RSpec::Core::RakeTask.new(:spec => 'app:db:test:prepare')
+
+task :default => :spec

data/app/controllers/robocall/application_controller.rb

@@ -0,0 +1,4 @@
+module Robocall
+  class ApplicationController < ActionController::Base
+  end
+end

data/app/controllers/robocall/robocalls_controller.rb

@@ -0,0 +1,87 @@
+require_dependency "robocall/application_controller"
+
+module Robocall
+  class RobocallsController < ApplicationController
+    # GET /robocalls
+    # GET /robocalls.json
+    def index
+      @robocalls = Robocall.all
+  
+      respond_to do |format|
+        format.html # index.html.erb
+        format.json { render json: @robocalls }
+      end
+    end
+  
+    # GET /robocalls/1
+    # GET /robocalls/1.json
+    def show
+      @robocall = Robocall.find(params[:id])
+  
+      respond_to do |format|
+        format.html # show.html.erb
+        format.json { render json: @robocall }
+      end
+    end
+  
+    # GET /robocalls/new
+    # GET /robocalls/new.json
+    def new
+      @robocall = Robocall.new
+  
+      respond_to do |format|
+        format.html # new.html.erb
+        format.json { render json: @robocall }
+      end
+    end
+  
+    # GET /robocalls/1/edit
+    def edit
+      @robocall = Robocall.find(params[:id])
+    end
+  
+    # POST /robocalls
+    # POST /robocalls.json
+    def create
+      @robocall = Robocall.new(params[:robocall])
+  
+      respond_to do |format|
+        if @robocall.save
+          format.html { redirect_to @robocall, notice: 'Robocall was successfully created.' }
+          format.json { render json: @robocall, status: :created, location: @robocall }
+        else
+          format.html { render action: "new" }
+          format.json { render json: @robocall.errors, status: :unprocessable_entity }
+        end
+      end
+    end
+  
+    # PUT /robocalls/1
+    # PUT /robocalls/1.json
+    def update
+      @robocall = Robocall.find(params[:id])
+  
+      respond_to do |format|
+        if @robocall.update_attributes(params[:robocall])
+          format.html { redirect_to @robocall, notice: 'Robocall was successfully updated.' }
+          format.json { head :no_content }
+        else
+          format.html { render action: "edit" }
+          format.json { render json: @robocall.errors, status: :unprocessable_entity }
+        end
+      end
+    end
+  
+    # DELETE /robocalls/1
+    # DELETE /robocalls/1.json
+    def destroy
+      @robocall = Robocall.find(params[:id])
+      @robocall.destroy
+  
+      respond_to do |format|
+        format.html { redirect_to robocalls_url }
+        format.json { head :no_content }
+      end
+    end
+  end
+end

data/app/helpers/robocall/application_helper.rb

@@ -0,0 +1,4 @@
+module Robocall
+  module ApplicationHelper
+  end
+end

data/app/models/robocall/robocall.rb

@@ -0,0 +1,13 @@
+require 'securerandom'
+
+module Robocall
+  class Robocall < ActiveRecord::Base
+    self.table_name = 'robocall_robocalls'
+    attr_accessible :token, :xml
+
+    def initialize(attributes = {})
+      super
+      self.token = SecureRandom.hex
+    end
+  end
+end

data/app/views/layouts/robocall/application.html.erb

@@ -0,0 +1,14 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <title>Robocall</title>
+  <%= stylesheet_link_tag    "robocall/application", :media => "all" %>
+  <%= javascript_include_tag "robocall/application" %>
+  <%= csrf_meta_tags %>
+</head>
+<body>
+
+<%= yield %>
+
+</body>
+</html>

data/config/routes.rb

@@ -0,0 +1,5 @@
+Rails.application.routes.draw do
+  resource :robocall, :only => [:connected_to_caller] do
+    post '/:call_id/:token' => 'robocall#connected_to_caller'
+  end
+end

data/db/migrate/20130807225623_create_robocall_robocalls.rb

@@ -0,0 +1,10 @@
+class CreateRobocallRobocalls < ActiveRecord::Migration
+  def change
+    create_table :robocall_robocalls do |t|
+      t.string :token
+      t.text :xml
+
+      t.timestamps
+    end
+  end
+end

data/lib/robocall.rb

@@ -0,0 +1,58 @@
+
+require 'twilio-ruby'
+require File.dirname(__FILE__) + "/../app/models/robocall/robocall"
+
+module Robocall
+  class << self
+    attr_accessor :sid, :auth_token, :from_phone_number, :base_path
+
+    def send_text(to: to, text: text, from: from_phone_number)
+      return true
+      twilio = get_twilio
+      twilio.account.sms.messages.create(
+        :from => from,
+        :to   => to,
+        :body => text
+      ) 
+    end
+
+    def send_robocall_xml(to: to, xml: xml, from: from_phone_number)
+      return true
+      twilio = get_twilio
+      # Store the xml in a record
+      debugger
+      callback_record = Robocall.new
+      debugger
+      callback_record.xml = xml
+      callback_record.save
+      # construct the callback URL
+      robocall_path(callback_record)
+      twilio.account.calls.create(
+        :from => from,
+        :to   => to,
+        :url  => url
+      )
+    end
+
+    def send_robocall(to: to, text: text, language: :english, from: from_phone_number)
+      return true
+      # Render XML
+      xml = "foo"
+      send_robocall_xml(to: to, xml: xml, from: from)
+    end
+
+    private
+
+    def get_twilio
+      verify_configuration_values(:sid, :auth_token, :from_phone_number)
+      return Twilio::REST::Client.new sid, auth_token
+    end
+
+    def verify_configuration_values(*symbols)
+      absent_values = symbols.select{|symbol| instance_variable_get("@#{symbol}").nil? }
+      raise("Must configure #{absent_values.join(", ")} before making this request.") unless absent_values.empty?
+    end
+
+  end
+
+end

data/lib/robocall/engine.rb

@@ -0,0 +1,12 @@
+module Robocall
+  class Engine < ::Rails::Engine
+    isolate_namespace Robocall
+
+    config.generators do |g|
+      g.test_framework      :rspec,        :fixture => false
+      g.fixture_replacement :factory_girl, :dir => 'spec/factories'
+      g.assets false
+      g.helper false
+    end
+  end
+end

data/lib/robocall/version.rb

@@ -0,0 +1,3 @@
+module Robocall
+  VERSION = "0.0.1"
+end

data/lib/tasks/robocall_tasks.rake

@@ -0,0 +1,4 @@
+# desc "Explaining what the task does"
+# task :robocall do
+#   # Task goes here
+# end

data/spec/controllers/robocall/robocalls_controller_spec.rb

@@ -0,0 +1,45 @@
+require 'spec_helper'
+
+module Robocall
+  describe RobocallsController do
+  
+    # This should return the minimal set of attributes required to create a valid
+    # Robocall. As you add validations to Robocall, be sure to
+    # adjust the attributes here as well.
+    let(:valid_attributes) { { 'token' => 'MyString', 'xml' => '<foo>' } }
+  
+    # This should return the minimal set of values that should be in the session
+    # in order to pass any filters (e.g. authentication) defined in
+    # RobocallsController. Be sure to keep this updated too.
+    let(:valid_session) { {} }
+  
+    describe "POST see response" do
+      describe "with valid params" do
+        it "returns the xml" do
+          expect {
+            post :create, {:robocall => valid_attributes}, valid_session
+          }.to change(Robocall, :count).by(1)
+        end
+  
+	it "cleans up the record after the callback has been received" do
+          pending
+	end
+      end
+  
+      describe "with invalid params" do
+        it "does not work when there's a token missmatch" do
+          pending
+        end
+  
+        it "does not work when there's no token" do
+          pending
+        end
+
+        it "does not work when there's no id" do
+          pending
+        end
+      end
+    end
+  
+  end
+end

data/spec/dummy/README.rdoc

@@ -0,0 +1,261 @@
+== Welcome to Rails
+
+Rails is a web-application framework that includes everything needed to create
+database-backed web applications according to the Model-View-Control pattern.
+
+This pattern splits the view (also called the presentation) into "dumb"
+templates that are primarily responsible for inserting pre-built data in between
+HTML tags. The model contains the "smart" domain objects (such as Account,
+Product, Person, Post) that holds all the business logic and knows how to
+persist themselves to a database. The controller handles the incoming requests
+(such as Save New Account, Update Product, Show Post) by manipulating the model
+and directing data to the view.
+
+In Rails, the model is handled by what's called an object-relational mapping
+layer entitled Active Record. This layer allows you to present the data from
+database rows as objects and embellish these data objects with business logic
+methods. You can read more about Active Record in
+link:files/vendor/rails/activerecord/README.html.
+
+The controller and view are handled by the Action Pack, which handles both
+layers by its two parts: Action View and Action Controller. These two layers
+are bundled in a single package due to their heavy interdependence. This is
+unlike the relationship between the Active Record and Action Pack that is much
+more separate. Each of these packages can be used independently outside of
+Rails. You can read more about Action Pack in
+link:files/vendor/rails/actionpack/README.html.
+
+
+== Getting Started
+
+1. At the command prompt, create a new Rails application:
+       <tt>rails new myapp</tt> (where <tt>myapp</tt> is the application name)
+
+2. Change directory to <tt>myapp</tt> and start the web server:
+       <tt>cd myapp; rails server</tt> (run with --help for options)
+
+3. Go to http://localhost:3000/ and you'll see:
+       "Welcome aboard: You're riding Ruby on Rails!"
+
+4. Follow the guidelines to start developing your application. You can find
+the following resources handy:
+
+* The Getting Started Guide: http://guides.rubyonrails.org/getting_started.html
+* Ruby on Rails Tutorial Book: http://www.railstutorial.org/
+
+
+== Debugging Rails
+
+Sometimes your application goes wrong. Fortunately there are a lot of tools that
+will help you debug it and get it back on the rails.
+
+First area to check is the application log files. Have "tail -f" commands
+running on the server.log and development.log. Rails will automatically display
+debugging and runtime information to these files. Debugging info will also be
+shown in the browser on requests from 127.0.0.1.
+
+You can also log your own messages directly into the log file from your code
+using the Ruby logger class from inside your controllers. Example:
+
+  class WeblogController < ActionController::Base
+    def destroy
+      @weblog = Weblog.find(params[:id])
+      @weblog.destroy
+      logger.info("#{Time.now} Destroyed Weblog ID ##{@weblog.id}!")
+    end
+  end
+
+The result will be a message in your log file along the lines of:
+
+  Mon Oct 08 14:22:29 +1000 2007 Destroyed Weblog ID #1!
+
+More information on how to use the logger is at http://www.ruby-doc.org/core/
+
+Also, Ruby documentation can be found at http://www.ruby-lang.org/. There are
+several books available online as well:
+
+* Programming Ruby: http://www.ruby-doc.org/docs/ProgrammingRuby/ (Pickaxe)
+* Learn to Program: http://pine.fm/LearnToProgram/ (a beginners guide)
+
+These two books will bring you up to speed on the Ruby language and also on
+programming in general.
+
+
+== Debugger
+
+Debugger support is available through the debugger command when you start your
+Mongrel or WEBrick server with --debugger. This means that you can break out of
+execution at any point in the code, investigate and change the model, and then,
+resume execution! You need to install ruby-debug to run the server in debugging
+mode. With gems, use <tt>sudo gem install ruby-debug</tt>. Example:
+
+  class WeblogController < ActionController::Base
+    def index
+      @posts = Post.all
+      debugger
+    end
+  end
+
+So the controller will accept the action, run the first line, then present you
+with a IRB prompt in the server window. Here you can do things like:
+
+  >> @posts.inspect
+  => "[#<Post:0x14a6be8
+          @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>,
+       #<Post:0x14a6620
+          @attributes={"title"=>"Rails", "body"=>"Only ten..", "id"=>"2"}>]"
+  >> @posts.first.title = "hello from a debugger"
+  => "hello from a debugger"
+
+...and even better, you can examine how your runtime objects actually work:
+
+  >> f = @posts.first
+  => #<Post:0x13630c4 @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>
+  >> f.
+  Display all 152 possibilities? (y or n)
+
+Finally, when you're ready to resume execution, you can enter "cont".
+
+
+== Console
+
+The console is a Ruby shell, which allows you to interact with your
+application's domain model. Here you'll have all parts of the application
+configured, just like it is when the application is running. You can inspect
+domain models, change values, and save to the database. Starting the script
+without arguments will launch it in the development environment.
+
+To start the console, run <tt>rails console</tt> from the application
+directory.
+
+Options:
+
+* Passing the <tt>-s, --sandbox</tt> argument will rollback any modifications
+  made to the database.
+* Passing an environment name as an argument will load the corresponding
+  environment. Example: <tt>rails console production</tt>.
+
+To reload your controllers and models after launching the console run
+<tt>reload!</tt>
+
+More information about irb can be found at:
+link:http://www.rubycentral.org/pickaxe/irb.html
+
+
+== dbconsole
+
+You can go to the command line of your database directly through <tt>rails
+dbconsole</tt>. You would be connected to the database with the credentials
+defined in database.yml. Starting the script without arguments will connect you
+to the development database. Passing an argument will connect you to a different
+database, like <tt>rails dbconsole production</tt>. Currently works for MySQL,
+PostgreSQL and SQLite 3.
+
+== Description of Contents
+
+The default directory structure of a generated Ruby on Rails application:
+
+  |-- app
+  |   |-- assets
+  |   |   |-- images
+  |   |   |-- javascripts
+  |   |   `-- stylesheets
+  |   |-- controllers
+  |   |-- helpers
+  |   |-- mailers
+  |   |-- models
+  |   `-- views
+  |       `-- layouts
+  |-- config
+  |   |-- environments
+  |   |-- initializers
+  |   `-- locales
+  |-- db
+  |-- doc
+  |-- lib
+  |   |-- assets
+  |   `-- tasks
+  |-- log
+  |-- public
+  |-- script
+  |-- test
+  |   |-- fixtures
+  |   |-- functional
+  |   |-- integration
+  |   |-- performance
+  |   `-- unit
+  |-- tmp
+  |   `-- cache
+  |       `-- assets
+  `-- vendor
+      |-- assets
+      |   |-- javascripts
+      |   `-- stylesheets
+      `-- plugins
+
+app
+  Holds all the code that's specific to this particular application.
+
+app/assets
+  Contains subdirectories for images, stylesheets, and JavaScript files.
+
+app/controllers
+  Holds controllers that should be named like weblogs_controller.rb for
+  automated URL mapping. All controllers should descend from
+  ApplicationController which itself descends from ActionController::Base.
+
+app/models
+  Holds models that should be named like post.rb. Models descend from
+  ActiveRecord::Base by default.
+
+app/views
+  Holds the template files for the view that should be named like
+  weblogs/index.html.erb for the WeblogsController#index action. All views use
+  eRuby syntax by default.
+
+app/views/layouts
+  Holds the template files for layouts to be used with views. This models the
+  common header/footer method of wrapping views. In your views, define a layout
+  using the <tt>layout :default</tt> and create a file named default.html.erb.
+  Inside default.html.erb, call <% yield %> to render the view using this
+  layout.
+
+app/helpers
+  Holds view helpers that should be named like weblogs_helper.rb. These are
+  generated for you automatically when using generators for controllers.
+  Helpers can be used to wrap functionality for your views into methods.
+
+config
+  Configuration files for the Rails environment, the routing map, the database,
+  and other dependencies.
+
+db
+  Contains the database schema in schema.rb. db/migrate contains all the
+  sequence of Migrations for your schema.
+
+doc
+  This directory is where your application documentation will be stored when
+  generated using <tt>rake doc:app</tt>
+
+lib
+  Application specific libraries. Basically, any kind of custom code that
+  doesn't belong under controllers, models, or helpers. This directory is in
+  the load path.
+
+public
+  The directory available for the web server. Also contains the dispatchers and the
+  default HTML files. This should be set as the DOCUMENT_ROOT of your web
+  server.
+
+script
+  Helper scripts for automation and generation.
+
+test
+  Unit and functional tests along with fixtures. When using the rails generate
+  command, template test files will be generated for you and placed in this
+  directory.
+
+vendor
+  External libraries that the application depends on. Also includes the plugins
+  subdirectory. If the app has frozen rails, those gems also go here, under
+  vendor/rails/. This directory is in the load path.