telegram-bot 0.7.2 → 0.7.3

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: 5f435d8f9b79fbaf3bd5f5b2fce82c96c64be1d6
4
- data.tar.gz: 29fbc530b43dca4b39d27ad69fd2ef4cade4ce15
3
+ metadata.gz: f550ace5be36284dfc7fdfc2e2f3adb23056d26a
4
+ data.tar.gz: 5da2c1fb644f836323c2deba45bb9c28c417e9dc
5
5
  SHA512:
6
- metadata.gz: 50b1cf3174f36b9c0dbfa2eb6b33cdc5a9b9352b18c6b24c7e7acca0e5fb29bddfd50c0b4199f7f33fb71f91c771ffb0b0894c99d287664ba48d9dc39f7fa39a
7
- data.tar.gz: 06ebe8d059e5ddf23e2648d5cdbdae3f2d85096789a7b93b893a9e96b19debcd6e338ac531a1a67282a7611b443487b33720caf52688938656dcedb793c0200a
6
+ metadata.gz: b020241a722c0c4d646370e85d7d7eab43ac5a303eb527b76ba9fcfd55f32d8453718854362860761a753bd4107275040ef0557c770de62796a3eab892028985
7
+ data.tar.gz: 8602c390dd685733f53f549bd9d12e829731d4808dcd915aa2b3b5e86b24b33f78ee15a0183083935ef9c3743322131d6713988a8baa554586d1ec1ecc49eb46
data/CHANGELOG.md CHANGED
@@ -1,3 +1,7 @@
1
+ # 0.7.3
2
+
3
+ - Fixed issues with poller in production (#3)
4
+
1
5
  # 0.7.2
2
6
 
3
7
  - Bot API 2.1
@@ -1,9 +1,14 @@
1
1
  namespace :telegram do
2
2
  namespace :bot do
3
- desc 'Run poller'
4
- task poller: :environment do
5
- console = ActiveSupport::Logger.new(STDERR)
6
- Rails.logger.extend ActiveSupport::Logger.broadcast console
3
+ desc 'Run poller. It broadcasts Rails.logger to STDOUT in dev like `rails s` do. ' \
4
+ 'Use LOG_TO_STDOUT to enable/disable broadcasting.'
5
+ task :poller do
6
+ ENV['BOT_POLLER_MODE'] = 'true'
7
+ Rake::Task['environment'].invoke
8
+ if ENV.fetch('LOG_TO_STDOUT') { Rails.env.development? }.present?
9
+ console = ActiveSupport::Logger.new(STDERR)
10
+ Rails.logger.extend ActiveSupport::Logger.broadcast console
11
+ end
7
12
  Telegram::Bot::UpdatesPoller.start(ENV['BOT'].try!(:to_sym) || :default)
8
13
  end
9
14
 
@@ -14,9 +14,14 @@ module Telegram
14
14
  # It just tells routes helpers whether to add routed bots to
15
15
  # Bot::UpdatesPoller, so their config will be available by bot key in
16
16
  # Bot::UpdatesPoller.start.
17
+ #
18
+ # It's enabled by default in Rails dev environment and `rake telegram:bot:poller`
19
+ # task. Use `BOT_POLLER_MODE=true` envvar to set it manually.
17
20
  def bot_poller_mode?
18
21
  return @bot_poller_mode if defined?(@bot_poller_mode)
19
- Rails.env.development? if defined?(Rails)
22
+ @bot_poller_mode = ENV.fetch('BOT_POLLER_MODE') do
23
+ Rails.env.development? if defined?(Rails)
24
+ end
20
25
  end
21
26
 
22
27
  # Hash of bots made with bots_config.
@@ -1,6 +1,6 @@
1
1
  module Telegram
2
2
  module Bot
3
- VERSION = '0.7.2'.freeze
3
+ VERSION = '0.7.3'.freeze
4
4
 
5
5
  def self.gem_version
6
6
  Gem::Version.new VERSION
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: telegram-bot
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.7.2
4
+ version: 0.7.3
5
5
  platform: ruby
6
6
  authors:
7
7
  - Max Melentiev