oceanex-slanger 0.7.1.3 → 0.7.1.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 5e94b170fa4ca189ff90da97498233d1c6af1d7159936510d17af03a259c47df
-  data.tar.gz: 4779c219ae6bb37e49194b8ae16e1152d261663b0a0932669fcc78e8bc132df5
+  metadata.gz: b8d982e2c189e52f3905e70cdcb0b4c9c00cbbe2cc7b173769ad547cecc58773
+  data.tar.gz: 8e045a72b30957002c11ba9015d5dc9fd06dbfe0b29274bbbd03cd67fa6a457e
 SHA512:
-  metadata.gz: 9447c272e597b97e5ec57939f4b401bfebe3ddd19cf00eb31465984951c1d276d2019d5c7ee01c1c3b7240ca3875042e046d12e54e826ac6f9748f4ca98b50f7
-  data.tar.gz: 0ec1b39904ebe373b5d09051fa9f987f2684c83aca0fd5b41f7042af30b1a6f09db3bb44401a9f2f1a6617a4a912b1d287e1cf4db2587ec7719adc7d69cbac89
+  metadata.gz: 883726b3449fa3f622aa9dbf5a380e7cfc7688bf660d6420d5bdeefdd8247049e958943ac0442d2d17591eca06993f77d1c532189b9bd5f520ef2839ee58e70d
+  data.tar.gz: ca574e7bec766e86e5d3ef783c46f7cfaa558e7be5b0fed6a81f6985859d222ab21a907537c04f7b5ed322f79c456e8c5cca3cb0dc6fddb2dabc6868ef3a0f4a

data/README.md

@@ -1,10 +1,11 @@
 # OceanEx Slanger
+[![Gem Version](https://badge.fury.io/rb/oceanex-slanger.svg)](https://badge.fury.io/rb/oceanex-slanger) [![Build Status](https://travis-ci.com/jobleeyoui/slanger.svg?branch=master)](https://travis-ci.com/jobleeyoui/slanger)
 
 The OceanEx Slanger inherits from the unmaintained Slanger. The project is backed by OceanEx dev team.
 
 We will do regularly bug fixes and security updates. 
 
-We might future add more features or provide performance improvements for OceanEx Slanger. The maintenance will continue until we find better option. 
+We might further add more features or provide performance improvements for OceanEx Slanger. The maintenance will continue until we find better option. 
 
 Feel free to log any issue or contribute to the code base.
 
@@ -57,8 +58,7 @@ rbenv install 2.6.3
 rbenv global 2.6.3
 ```
 
-Usually, install the Oceanex Slanger should be pretty easy with the following command. OceanEx Slanger is just a variation of the unmaintained Slanger.
-The execution kept the same way as before. Please check our release note to see what is new in additional to the unmaintained Slanger. 
+Then install the OceanEx Slanger
 
 ```
 gem install oceanex-slanger
@@ -66,7 +66,7 @@ gem install oceanex-slanger
 
 ### Mac
 
-Install the ruby version via brew
+Install the ruby version via home brew
 
 ```
 brew install ruby
@@ -79,8 +79,7 @@ rbenv install 2.6.3
 rbenv global 2.6.3
 ```
 
-Installation should be pretty straightforward on linux, however, install OceanEx Slanger might fail on mac os.
-This is due to the c compiler converts the warning to error when building the native extension.
+Installation might fail when some dependent gems builds their native extension. This is due to the c compiler converts the warning to error when do so.
 
 If you see installation fails due to `implicit-function-declaration`, you could try the following step to suppress the warning.
 
@@ -93,7 +92,7 @@ gem install oceanex-slanger -- --with-cflags="-Wno-error=implicit-function-decla
 Both the app key and app secret are just random string, you could choose any string. However, it is recommended to be long
 enough to keep secure.
 
-Oceanex slanger also depends on redis service, specify the redis url when launching the OceanEx Slanger. 
+Oceanex Slanger also depends on redis service, specify the redis url when launching the OceanEx Slanger. 
 
 ```
 slanger --app_key $APP_KEY --secret $APP_SECRET -r $REDIS_URL
@@ -122,7 +121,7 @@ Slanger WebSocket server listening on port 8080
 
 ## Start the OceanEx Slanger in Docker environment 
 
-The OceanEx slanger supports running in docker environment and such approach is already encapsulated in the make command.
+The OceanEx Slanger supports running in docker environment and such approach is already encapsulated in the make command.
 The dependent Redis docker image is also automatically downloaded and started.
 
 For the app key and app secret, please check `docker-compose.yaml` and modify as needed.
@@ -142,10 +141,9 @@ make up
 make down
 ```
 
-## Modifying your application code to use the Slanger service
-
-Once you have a Slanger instance listening for incoming connections you need to alter you application code to use the Slanger endpoint instead of Pusher. Fortunately this is very simple, unobtrusive, easily reversable, and very painless.
+## Modifying your application code to use the OceanEx Slanger service
 
+Once you have a OceanEx Slanger instance listening for incoming connections you need to alter you application code to use the OceanEx Slanger endpoint instead of Pusher. Fortunately this is very simple, unobtrusive, easily reversable, and very painless.
 
 First you will need to add code to your server side component that publishes events to the Pusher HTTP REST API, usually this means telling the Pusher client to use a different host and port, e.g. consider this Ruby example
 
@@ -173,7 +171,7 @@ Of course you could proxy all requests to `ws.example.com` to port 8080 of your
 
 # Configuration Options
 
-Slanger supports several configuration options, which can be supplied as command line arguments at invocation. You can also supply a yaml file containing config options. If you use the config file in combination with other configuration options, the values passed on the command line will win. Allows running multiple instances with only a few differences easy.
+OceanEx Slanger supports several configuration options, which can be supplied as command line arguments at invocation. You can also supply a yaml file containing config options. If you use the config file in combination with other configuration options, the values passed on the command line will win. Allows running multiple instances with only a few differences easy.
 
 ```
 -k or --app_key This is the Pusher app key you want to use. This is a required argument on command line or in optional config file
@@ -201,21 +199,6 @@ Slanger supports several configuration options, which can be supplied as command
 --pid_file  The path to a file you want slanger to write it's PID to. Optional.
 ```
 
-# Why use Slanger instead of Pusher?
-
-There a few reasons you might want to use Slanger instead of Pusher, e.g.
-
-- You operate in a heavily regulated industry and are worried about sending data to 3rd parties, and it is an organisational requirement that you own your own infrastructure.
-- You might be travelling on an airplane without internet connectivity as I am right now. Airplane rides are very good times to get a lot done, unfortunately external services are also usually unreachable. Remove internet connectivity as a dependency of your development envirionment by running a local Slanger instance in development and Pusher in production.
-- Remove the network dependency from your test suite.
-- You want to extend the Pusher protocol or have some special requirement. If this applies to you, chances are you are out of luck as Pusher is unlikely to implement something to suit your special use case, and rightly so. With Slanger you are free to modify and extend its behavior anyway that suits your purpose.
-
-# Why did you write Slanger
-
-I wanted to write a non-trivial evented app. I also want to write a book on evented programming in Ruby as I feel there is scant good information available on the topic and this project is handy to show publishers.
-
-Pusher is an awesome service, very reasonably priced, and run by an awesome crew. Give them a spin on your next project.
-
 # Original Author
 
 - Stevie Graham
@@ -232,8 +215,11 @@ Pusher is an awesome service, very reasonably priced, and run by an awesome crew
 - Florian Gilcher
 - Claudio Poli
 
-# Current Author and Maintainer
-- joblee
+# Current Core Team and Contributor
+- Joblee
+- Steve
+- Yao
+- Meng
 
 
-© 2020 a joblee joint.
+© 2020 a OceanEx joint.

data/lib/slanger/version.rb

@@ -1,3 +1,3 @@
 module Slanger
-  VERSION = "0.7.1.3"
+  VERSION = "0.7.1.4"
 end

metadata

@@ -1,14 +1,17 @@
 --- !ruby/object:Gem::Specification
 name: oceanex-slanger
 version: !ruby/object:Gem::Version
-  version: 0.7.1.3
+  version: 0.7.1.4
 platform: ruby
 authors:
-- joblee
+- Joblee
+- Steve
+- Yao
+- Meng
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2020-09-13 00:00:00.000000000 Z
+date: 2020-09-15 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: eventmachine
@@ -142,14 +145,14 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 1.1.6
+        version: 1.1.7
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 1.1.6
+        version: 1.1.7
 - !ruby/object:Gem::Dependency
   name: oj
   requirement: !ruby/object:Gem::Requirement
@@ -304,7 +307,7 @@ dependencies:
     - - "~>"
       - !ruby/object:Gem::Version
         version: 13.0.1
-description: The oceanex slanger inherits from unmaintained project slanger and continue
+description: The Oceanex Slanger inherits from unmaintained project Slanger and continue
   to provide update and fixes
 email:
 - jobleeyoui@gmail.com
@@ -349,13 +352,13 @@ files:
 - spec/unit/channel_spec.rb
 - spec/unit/request_validation_spec.rb
 - spec/unit/webhook_spec.rb
-homepage: https://github.com/jobleeyoui/oceanex-slanger
+homepage: https://github.com/OceanEx/slanger
 licenses:
 - MIT
 metadata:
-  homepage_uri: https://github.com/jobleeyoui/oceanex-slanger
-  source_code_uri: https://github.com/jobleeyoui/oceanex-slanger/archive/v0.7.1.1.zip
-  changelog_uri: https://github.com/jobleeyoui/oceanex-slanger/releases
+  homepage_uri: https://github.com/OceanEx/slanger
+  source_code_uri: https://github.com/OceanEx/slanger/archive/v0.7.1.4.zip
+  changelog_uri: https://github.com/OceanEx/slanger/releases
 post_install_message: 
 rdoc_options: []
 require_paths: