newmen/sms24x7

Sending SMS via sms24x7.ru API

Sms24x7

Sending SMS via sms24x7 API. For more details see http://sms24x7.ru/api/

Installation

Add this line to your application's Gemfile:

gem 'sms24x7'

And then execute:

$ bundle

Or install it yourself as:

$ gem install sms24x7

Usage

In the begining, you need to register for sending SMS through sms24x7 gateway.

Before sending SMS, you need to configure SmsApi with login credentials:

SmsApi.setup do |config|
  config.email = '[email protected]'
  config.password = 'your_password'
end

There are two ways for sending your SMS.

The first - it's sending a SMS to one recipient. To do this, use:

SmsApi.push_msg_nologin('recipient_phone', 'sms_text', params)

here recipient_phone - is a phone number in format '7xxxyyyzzzz' and params - additional params that you can see in documentation.

The second way - it's sending multiple SMS to multiple recipients.

SmsApi.login do
  recipient_phones_str_arr.each do |recipient_phone|
    SmsApi.push_msg(recipient_phone, 'sms_text', params)
  end
end

here recipient_phones_str_arr - it's array that consist phone numbers as strings in format that represented above.

License

sms24x7 ruby gem is licensed under the BSD License.

sms24x7's Issues

License missing from gemspec

RubyGems.org doesn't report a license for your gem. This is because it is not specified in the gemspec of your last release.

via e.g.

  spec.license = 'MIT'
  # or
  spec.licenses = ['MIT', 'GPL-2']

Including a license in your gemspec is an easy way for rubygems.org and other tools to check how your gem is licensed. As you can imagine, scanning your repository for a LICENSE file or parsing the README, and then attempting to identify the license or licenses is much more difficult and more error prone. So, even for projects that already specify a license, including a license in your gemspec is a good practice. See, for example, how rubygems.org uses the gemspec to display the rails gem license.

There is even a License Finder gem to help companies/individuals ensure all gems they use meet their licensing needs. This tool depends on license information being available in the gemspec. This is an important enough issue that even Bundler now generates gems with a default 'MIT' license.

I hope you'll consider specifying a license in your gemspec. If not, please just close the issue with a nice message. In either case, I'll follow up. Thanks for your time!

Appendix:

If you need help choosing a license (sorry, I haven't checked your readme or looked for a license file), GitHub has created a license picker tool. Code without a license specified defaults to 'All rights reserved'-- denying others all rights to use of the code.
Here's a list of the license names I've found and their frequencies

p.s. In case you're wondering how I found you and why I made this issue, it's because I'm collecting stats on gems (I was originally looking for download data) and decided to collect license metadata,too, and make issues for gemspecs not specifying a license as a public service :). See the previous link or my blog post about this project for more information.