r7kamura / ruboty Goto Github PK

View Code? Open in Web Editor NEW

459.0 37.0 60.0 617 KB

Ruby + Bot = Ruboty

License: MIT License

Ruby 100.00%

ruboty's Introduction

Ruboty

Ruby + Bot = Ruboty.

Dependencies

Ruby 2.2.2

Adapter

Adapter hooks up ruboty to chat services.

Slack
- ruboty-slack (XMPP gateway)
- ruboty-slack_rtm (Bot RTM API)
ruboty-twitter
ruboty-hipchat
ruboty-idobata
ruboty-chatwork
ruboty-discord

Brain

Brain persists memories.

Handler

Handler provides various behaviors.

Other plugins are hosted on Rubygems.

Configuration

Store configuration value in envorinment variables. They are easy to change between deploys without changing any code. We recommend to put .env and run with ruboty --dotenv option to manage them .

All you need to use your favorite plugins is to write their names into Gemfile. Ruboty will load them before running.

# Gemfile
gem "ruboty-cron"
gem "ruboty-google_image"
gem "ruboty-redis"
gem "ruboty-slack"

ENV

DISABLE_DEFAULT_HANDLERS - Pass 1 to disable default handlers (default: nil)
LOG_LEVEL                - Log level for debug (default: 3)
RUBOTY_ENV               - Loaded gem group name (default: development)
RUBOTY_NAME              - Name to respond to mention (default: ruboty)

Deploy

See r7kamura/ruboty-template for example.

ruboty's People

Contributors

Stargazers

Watchers

ruboty's Issues

Dummy issue to test GitHub API

Rename: Ellen -> Ruboty

Error of load option with slop v4.0.0

Hi. Some problems occur, using --load option with slop 4.0.0.

1) A case the problems have occured

Gemfile

source "https://rubygems.org"
gem "ruboty"

handlers.rb

puts "handlers.rb is loaded!"

slop version

$ bundle list | grep slop
  * slop (4.0.0)

run ruboty

Running with long option --load, Slop::UnknownOption occurs:

$ bundle exec ruboty --load handlers.rb
/Users/nownabe/ruboty/vendor/bundle/ruby/2.2.0/gems/slop-4.0.0/lib/slop/parser.rb:98:in `try_process': unknown option `--load' (Slop::UnknownOption)
    from /Users/nownabe/ruboty/vendor/bundle/ruby/2.2.0/gems/slop-4.0.0/lib/slop/parser.rb:53:in `block in parse'
    from /Users/nownabe/ruboty/vendor/bundle/ruby/2.2.0/gems/slop-4.0.0/lib/slop/parser.rb:44:in `each'
    from /Users/nownabe/ruboty/vendor/bundle/ruby/2.2.0/gems/slop-4.0.0/lib/slop/parser.rb:44:in `parse'
    from /Users/nownabe/ruboty/vendor/bundle/ruby/2.2.0/gems/slop-4.0.0/lib/slop/options.rb:71:in `parse'
    from /Users/nownabe/ruboty/vendor/bundle/ruby/2.2.0/gems/slop-4.0.0/lib/slop.rb:24:in `parse'
    from /Users/nownabe/ruboty/vendor/bundle/ruby/2.2.0/gems/ruboty-1.1.4/lib/ruboty/command_builder.rb:29:in `options'
    from /Users/nownabe/ruboty/vendor/bundle/ruby/2.2.0/gems/mem-0.1.5/lib/mem.rb:44:in `block in memoize'
    from /Users/nownabe/ruboty/vendor/bundle/ruby/2.2.0/gems/ruboty-1.1.4/lib/ruboty/command_builder.rb:19:in `command_class'
    from /Users/nownabe/ruboty/vendor/bundle/ruby/2.2.0/gems/ruboty-1.1.4/lib/ruboty/command_builder.rb:12:in `build'
    from /Users/nownabe/ruboty/vendor/bundle/ruby/2.2.0/gems/ruboty-1.1.4/bin/ruboty:6:in `<top (required)>'
    from /Users/nownabe/ruboty/vendor/bundle/ruby/2.2.0/bin/ruboty:23:in `load'
    from /Users/nownabe/ruboty/vendor/bundle/ruby/2.2.0/bin/ruboty:23:in `<main>'

(bundle exec ruboty --load=handlers.rb raised same error.)

Running with short option -l, Slop::UnknownOption doesn't occure, but handlers.rb is not loaded.

$ bundle exec ruboty -l handlers.rb
Type `exit` or `quit` to end the session.
> exit

2) A case the same operation as 1) is completed with slop v3.6.0

Gemfile

source "https://rubygems.org"
gem "ruboty"
gem "slop", "~> 3.6"

handlers.rb

puts "handlers.rb is loaded!"

slop version

$ bundle list | grep slop
  * slop (3.6.0)

run ruboty

There is no problem with any load options (--load, --load= or -l):

$ bundle exec ruboty --load handlers.rb
handlers.rb is loaded!
Type `exit` or `quit` to end the session.
> exit

Error with slop 4.0.0

Hi. I was trying out ruboty, and facing the following errors at rake spec command (Error message is indicating that Slop.parse! is missing).

Failures:

  1) Ruboty::Commands::Generate#call with normal condition generates ./ruboty/ directory from our templates
     Failure/Error: Ruboty::CommandBuilder.new(arguments).build
     NoMethodError:
       undefined method `parse!' for Slop:Module
     # ./lib/ruboty/command_builder.rb:22:in `options'
     # ./lib/ruboty/command_builder.rb:18:in `command_class'
     # ./lib/ruboty/command_builder.rb:12:in `build'
     # ./spec/ruboty/commands/generate_spec.rb:10:in `block (3 levels) in <top (required)>'
     # ./spec/ruboty/commands/generate_spec.rb:14:in `block (3 levels) in <top (required)>'
     # ./spec/ruboty/commands/generate_spec.rb:23:in `block (4 levels) in <top (required)>'

...2 more errors continue...

It seems the newer slop is just released (with some breaking changes), and causing the error. It may be good to limit the slop version, or adjust the code to latest version?

Some notes are,

It seems the 4.0.0 is released on 12/27
- https://rubygems.org/gems/slop/versions/4.0.0
The last section of the readme is indicating Slop.parse! deprecation.
- https://github.com/leejarvis/slop
I used ruby 2.2.0/2.0.0, and both were the same result.

r7kamura / ruboty Goto Github PK

ruboty's Introduction

Ruboty

Dependencies

Adapter

Brain

Handler

Configuration

ENV

Deploy

ruboty's People

Contributors

Stargazers

Watchers

Forkers

ruboty's Issues

1) A case the problems have occured

Gemfile

handlers.rb

slop version

run ruboty

2) A case the same operation as 1) is completed with slop v3.6.0

Gemfile

handlers.rb

slop version

run ruboty

Recommend Projects

Recommend Topics

Recommend Org