slack-ruby-bot-server 0.12.3 → 1.0.0

data/sample_apps/sample_app_activerecord/config/postgresql.yml

@@ -1,17 +0,0 @@
-default: &default
-  adapter: postgresql
-  pool: 10
-  timeout: 5000
-  encoding: unicode
-
-development:
-  <<: *default
-  database: slack_ruby_bot_server_development
-
-test:
-  <<: *default
-  database: slack_ruby_bot_server_test
-
-production:
-  <<: *default
-  url: <%= ENV["DATABASE_URL"] %>

data/sample_apps/sample_app_activerecord/db/migrate/20170307164946_create_teams_table.rb

@@ -1,12 +0,0 @@
-class CreateTeamsTable < ActiveRecord::Migration[5.0]
-  def change
-    create_table :teams, force: true do |t|
-      t.string :team_id
-      t.string :name
-      t.boolean :active, default: true
-      t.string :domain
-      t.string :token
-      t.timestamps
-    end
-  end
-end

data/sample_apps/sample_app_activerecord/db/migrate/20190323181453_add_activated_fields.rb

@@ -1,7 +0,0 @@
-class AddActivatedFields < ActiveRecord::Migration[5.0]
-  def change
-    add_column :teams, :bot_user_id, :string
-    add_column :teams, :activated_user_id, :string
-    add_column :teams, :activated_user_access_token, :string
-  end
-end

data/sample_apps/sample_app_activerecord/db/schema.rb

@@ -1,29 +0,0 @@
-# This file is auto-generated from the current state of the database. Instead
-# of editing this file, please use the migrations feature of Active Record to
-# incrementally modify your database, and then regenerate this schema definition.
-#
-# Note that this schema.rb definition is the authoritative source for your
-# database schema. If you need to create the application database on another
-# system, you should be using db:schema:load, not running all the migrations
-# from scratch. The latter is a flawed and unsustainable approach (the more migrations
-# you'll amass, the slower it'll run and the greater likelihood for issues).
-#
-# It's strongly recommended that you check this file into your version control system.
-
-ActiveRecord::Schema.define(version: 20_190_323_181_453) do
-  # These are extensions that must be enabled in order to support this database
-  enable_extension 'plpgsql'
-
-  create_table 'teams', force: :cascade do |t|
-    t.string   'team_id'
-    t.string   'name'
-    t.boolean  'active', default: true
-    t.string   'domain'
-    t.string   'token'
-    t.datetime 'created_at',                                 null: false
-    t.datetime 'updated_at',                                 null: false
-    t.string   'bot_user_id'
-    t.string   'activated_user_id'
-    t.string   'activated_user_access_token'
-  end
-end

data/sample_apps/sample_app_activerecord/spec/api/root_spec.rb

@@ -1,16 +0,0 @@
-require 'spec_helper'
-
-def app
-  SlackRubyBotServer::Api::Middleware.instance
-end
-
-describe 'API' do
-  include Rack::Test::Methods
-
-  it 'root' do
-    get '/api'
-    expect(last_response.status).to eq 200
-    links = JSON.parse(last_response.body)['_links']
-    expect(links.keys.sort).to eq(%w[self status team teams].sort)
-  end
-end

data/sample_apps/sample_app_activerecord/spec/commands/help_spec.rb

@@ -1,14 +0,0 @@
-require 'spec_helper'
-require 'commands/help'
-
-describe Help do
-  let!(:team) { Fabricate(:team) }
-  let(:app) { SlackRubyBotServer::Server.new(team: team) }
-  let(:client) { app.send(:client) }
-  let(:message_hook) { SlackRubyBot::Hooks::Message.new }
-  it 'default' do
-    expect(client).to receive(:say).with(channel: 'channel', text: [Help::HELP, SlackRubyBotServer::INFO].join("\n"))
-    expect(client).to receive(:say).with(channel: 'channel')
-    message_hook.call(client, Hashie::Mash.new(channel: 'channel', text: "#{SlackRubyBot.config.user} help"))
-  end
-end

data/sample_apps/sample_app_activerecord/spec/commands/whoami_spec.rb

@@ -1,14 +0,0 @@
-require 'spec_helper'
-require 'commands/whoami'
-
-describe Whoami do
-  let(:team) { Fabricate(:team) }
-  let(:app) { SlackRubyBotServer::Server.new(team: team) }
-  context 'whoami' do
-    it 'returns username' do
-      expect(message: "#{SlackRubyBot.config.user} whoami", channel: 'channel', user: 'user').to respond_with_slack_message(
-        '<@user>'
-      )
-    end
-  end
-end

data/sample_apps/sample_app_activerecord/spec/spec_helper.rb

@@ -1,19 +0,0 @@
-$LOAD_PATH.unshift File.expand_path('..', __dir__)
-
-ENV['RACK_ENV'] = 'test'
-
-require 'active_record'
-require 'database_cleaner'
-require 'slack-ruby-bot-server/rspec'
-
-db_config = YAML.safe_load(File.read(File.expand_path('../config/postgresql.yml', __dir__)), [], [], true)[ENV['RACK_ENV']]
-ActiveRecord::Tasks::DatabaseTasks.create(db_config)
-ActiveRecord::Base.establish_connection(db_config)
-
-RSpec.configure do |config|
-  config.around :each do |example|
-    DatabaseCleaner.cleaning do
-      example.run
-    end
-  end
-end

data/sample_apps/sample_app_mongoid/.rspec

@@ -1,3 +0,0 @@
---color
---format=documentation
-

data/sample_apps/sample_app_mongoid/Gemfile

@@ -1,20 +0,0 @@
-source 'https://rubygems.org'
-
-gem 'mongoid'
-gem 'newrelic-slack-ruby-bot'
-gem 'slack-ruby-bot-server', path: '../../'
-
-gem 'kaminari-mongoid'
-gem 'mongoid-scroll'
-gem 'unicorn'
-
-group :test do
-  gem 'database_cleaner'
-  gem 'fabrication'
-  gem 'faker'
-  gem 'rack-test'
-  gem 'rake'
-  gem 'rspec'
-  gem 'vcr'
-  gem 'webmock'
-end

data/sample_apps/sample_app_mongoid/Procfile

@@ -1 +0,0 @@
-web: bundle exec unicorn -p $PORT

data/sample_apps/sample_app_mongoid/README.md

@@ -1,14 +0,0 @@
-### What's this?
-
-This is a sample slack-ruby-bot-server with ActiveRecord.
-
-### Run
-
-```
-bundle install
-rackup
-```
-
-### Demo
-
-This app is deployed from [github.com/slack-ruby/slack-ruby-bot-server-sample](https://github.com/slack-ruby/slack-ruby-bot-server-sample).

data/sample_apps/sample_app_mongoid/Rakefile

@@ -1,10 +0,0 @@
-require 'rubygems'
-
-require 'rspec/core'
-require 'rspec/core/rake_task'
-
-RSpec::Core::RakeTask.new(:spec) do |spec|
-  spec.pattern = FileList['spec/**/*_spec.rb']
-end
-
-task default: [:spec]

data/sample_apps/sample_app_mongoid/commands.rb

@@ -1,2 +0,0 @@
-require_relative 'commands/help'
-require_relative 'commands/whoami'

data/sample_apps/sample_app_mongoid/commands/help.rb

@@ -1,19 +0,0 @@
-class Help < SlackRubyBot::Commands::Base
-  HELP = <<-EOS.freeze
-```
-I am your friendly slack-ruby-bot-server, here to help.
-
-General
--------
-
-help               - get this helpful message
-whoami             - print your username
-
-```
-  EOS
-  def self.call(client, data, _match)
-    client.say(channel: data.channel, text: [HELP, SlackRubyBotServer::INFO].join("\n"))
-    client.say(channel: data.channel)
-    logger.info "HELP: #{client.owner}, user=#{data.user}"
-  end
-end

data/sample_apps/sample_app_mongoid/commands/whoami.rb

@@ -1,6 +0,0 @@
-class Whoami < SlackRubyBot::Commands::Base
-  def self.call(client, data, _match)
-    client.say(channel: data.channel, text: "<@#{data.user}>")
-    logger.info "UNAME: #{client.owner}, user=#{data.user}"
-  end
-end

data/sample_apps/sample_app_mongoid/config.ru

@@ -1,14 +0,0 @@
-ENV['RACK_ENV'] ||= 'development'
-
-Bundler.require :default
-
-require_relative 'commands'
-
-Mongoid.load!(File.expand_path('config/mongoid.yml', __dir__), ENV['RACK_ENV'])
-
-NewRelic::Agent.manual_start
-
-SlackRubyBotServer::App.instance.prepare!
-SlackRubyBotServer::Service.start!
-
-run SlackRubyBotServer::Api::Middleware.instance

data/sample_apps/sample_app_mongoid/config/mongoid.yml

@@ -1,27 +0,0 @@
-development:
-  clients:
-    default:
-      database: bot-server_development
-      hosts:
-        - 127.0.0.1:27017
-  options:
-    raise_not_found_error: false
-    use_utc: true
-
-test:
-  clients:
-    default:
-      database: bot-server_test
-      hosts:
-        - 127.0.0.1:27017
-  options:
-    raise_not_found_error: false
-    use_utc: true
-
-production:
-  clients:
-    default:
-      uri: <%= ENV['MONGO_URL'] || ENV['MONGOHQ_URI'] || ENV['MONGOLAB_URI'] || ENV['MONGODB_URI'] %>
-  options:
-    raise_not_found_error: false
-    use_utc: true

data/sample_apps/sample_app_mongoid/config/newrelic.yml

@@ -1,217 +0,0 @@
-# Here are the settings that are common to all environments
-common: &default_settings
-  # ============================== LICENSE KEY ===============================
-
-  # You must specify the license key associated with your New Relic
-  # account.  This key binds your Agent's data to your account in the
-  # New Relic service.
-  license_key: '<%= ENV["NEW_RELIC_LICENSE_KEY"] %>'
-
-  # Application Name Set this to be the name of your application as
-  # you'd like it show up in New Relic. The service will then auto-map
-  # instances of your application into an "application" on your
-  # dashboard page. If you want to map this instance into multiple
-  # apps, like "AJAX Requests" and "All UI" then specify a semicolon
-  # separated list of up to three distinct names, or a yaml list.
-  app_name: <%= ENV["NEW_RELIC_APP_NAME"] || 'SlackRubyBotServer' %>
-
-  # When "true", the agent collects performance data about your
-  # application and reports this data to the New Relic service at
-  # newrelic.com. This global switch is normally overridden for each
-  # environment below. (formerly called 'enabled')
-  monitor_mode: true
-
-  # Developer mode should be off in every environment but
-  # development as it has very high overhead in memory.
-  developer_mode: false
-
-  # The newrelic agent generates its own log file to keep its logging
-  # information separate from that of your application.  Specify its
-  # log level here.
-  log_level: info
-
-  # Optionally set the path to the log file This is expanded from the
-  # root directory (may be relative or absolute, e.g. 'log/' or
-  # '/var/log/') The agent will attempt to create this directory if it
-  # does not exist.
-  # log_file_path: 'log'
-
-  # Optionally set the name of the log file, defaults to 'newrelic_agent.log'
-  # log_file_name: 'newrelic_agent.log'
-
-  # The newrelic agent communicates with the service via http by
-  # default.  If you want to communicate via https to increase
-  # security, then turn on SSL by setting this value to true.  Note,
-  # this will result in increased CPU overhead to perform the
-  # encryption involved in SSL communication, but this work is done
-  # asynchronously to the threads that process your application code,
-  # so it should not impact response times.
-  ssl: false
-
-  # EXPERIMENTAL: enable verification of the SSL certificate sent by
-  # the server. This setting has no effect unless SSL is enabled
-  # above. This may block your application. Only enable it if the data
-  # you send us needs end-to-end verified certificates.
-  #
-  # This means we cannot cache the DNS lookup, so each request to the
-  # service will perform a lookup. It also means that we cannot
-  # use a non-blocking lookup, so in a worst case, if you have DNS
-  # problems, your app may block indefinitely.
-  # verify_certificate: true
-
-  # Set your application's Apdex threshold value with the 'apdex_t'
-  # setting, in seconds. The apdex_t value determines the buckets used
-  # to compute your overall Apdex score.
-  # Requests that take less than apdex_t seconds to process will be
-  # classified as Satisfying transactions; more than apdex_t seconds
-  # as Tolerating transactions; and more than four times the apdex_t
-  # value as Frustrating transactions.
-  # For more about the Apdex standard, see
-  # http://newrelic.com/docs/general/apdex
-
-  apdex_t: 0.5
-
-  #============================== Browser Monitoring ===============================
-  # New Relic Real User Monitoring gives you insight into the performance real users are
-  # experiencing with your website. This is accomplished by measuring the time it takes for
-  # your users' browsers to download and render your web pages by injecting a small amount
-  # of JavaScript code into the header and footer of each page.
-  browser_monitoring:
-      # By default the agent automatically injects the monitoring JavaScript
-      # into web pages. Set this attribute to false to turn off this behavior.
-      auto_instrument: true
-
-  # Proxy settings for connecting to the service.
-  #
-  # If a proxy is used, the host setting is required.  Other settings
-  # are optional.  Default port is 8080.
-  #
-  # proxy_host: hostname
-  # proxy_port: 8080
-  # proxy_user:
-  # proxy_pass:
-
-
-  # Tells transaction tracer and error collector (when enabled)
-  # whether or not to capture HTTP params.  When true, frameworks can
-  # exclude HTTP parameters from being captured.
-  # Rails: the RoR filter_parameter_logging excludes parameters
-  # Java: create a config setting called "ignored_params" and set it to
-  #     a comma separated list of HTTP parameter names.
-  #     ex: ignored_params: credit_card, ssn, password
-  capture_params: true
-
-
-  # Transaction tracer captures deep information about slow
-  # transactions and sends this to the service once a
-  # minute. Included in the transaction is the exact call sequence of
-  # the transactions including any SQL statements issued.
-  transaction_tracer:
-
-    # Transaction tracer is enabled by default. Set this to false to
-    # turn it off. This feature is only available at the Professional
-    # and above product levels.
-    enabled: true
-
-    # Threshold in seconds for when to collect a transaction
-    # trace. When the response time of a controller action exceeds
-    # this threshold, a transaction trace will be recorded and sent to
-    # the service. Valid values are any float value, or (default)
-    # "apdex_f", which will use the threshold for an dissatisfying
-    # Apdex controller action - four times the Apdex T value.
-    transaction_threshold: apdex_f
-
-    # When transaction tracer is on, SQL statements can optionally be
-    # recorded. The recorder has three modes, "off" which sends no
-    # SQL, "raw" which sends the SQL statement in its original form,
-    # and "obfuscated", which strips out numeric and string literals
-    record_sql: obfuscated
-
-    # Threshold in seconds for when to collect stack trace for a SQL
-    # call. In other words, when SQL statements exceed this threshold,
-    # then capture and send the current stack trace. This is
-    # helpful for pinpointing where long SQL calls originate from
-    stack_trace_threshold: 0.500
-
-    # Determines whether the agent will capture query plans for slow
-    # SQL queries.  Only supported in mysql and postgres.  Should be
-    # set to false when using other adapters.
-    # explain_enabled: true
-
-    # Threshold for query execution time below which query plans will not
-    # not be captured.  Relevant only when `explain_enabled` is true.
-    # explain_threshold: 0.5
-
-  # Error collector captures information about uncaught exceptions and
-  # sends them to the service for viewing
-  error_collector:
-
-    # Error collector is enabled by default. Set this to false to turn
-    # it off. This feature is only available at the Professional and above
-    # product levels
-    enabled: true
-
-    # Rails Only - tells error collector whether or not to capture a
-    # source snippet around the place of the error when errors are View
-    # related.
-    capture_source: true
-
-    # To stop specific errors from reporting to New Relic, set this property
-    # to comma separated values.  Default is to ignore routing errors
-    # which are how 404's get triggered.
-    #
-    ignore_errors: ActionController::RoutingError
-
-  # (Advanced) Uncomment this to ensure the cpu and memory samplers
-  # won't run.  Useful when you are using the agent to monitor an
-  # external resource
-  # disable_samplers: true
-
-  # If you aren't interested in visibility in these areas, you can
-  # disable the instrumentation to reduce overhead.
-  #
-  # disable_view_instrumentation: true
-  # disable_activerecord_instrumentation: true
-  # disable_memcache_instrumentation: true
-  # disable_dj: true
-
-  # If you're interested in capturing memcache keys as though they
-  # were SQL uncomment this flag. Note that this does increase
-  # overhead slightly on every memcached call, and can have security
-  # implications if your memcached keys are sensitive
-  # capture_memcache_keys: true
-
-  # Certain types of instrumentation such as GC stats will not work if
-  # you are running multi-threaded.  Please let us know.
-  # multi_threaded = false
-
-# Application Environments
-# ------------------------------------------
-
-development:
-  <<: *default_settings
-  # Turn off communication to New Relic service in development mode (also
-  # 'enabled').
-  # NOTE: for initial evaluation purposes, you may want to temporarily
-  # turn the agent on in development mode.
-  monitor_mode: false
-
-  # Rails Only - when running in Developer Mode, the New Relic Agent will
-  # present performance information on the last 100 transactions you have
-  # executed since starting the mongrel.
-  # NOTE: There is substantial overhead when running in developer mode.
-  # Do not use for production or load testing.
-  developer_mode: true
-
-  # Enable textmate links
-  # textmate: true
-
-test:
-  <<: *default_settings
-  # It almost never makes sense to turn on the agent when running
-  # unit, functional or integration tests or the like.
-  monitor_mode: false
-
-production:
-  <<: *default_settings
-  monitor_mode: true