token_master 0.1.3 → 1.0.0

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: e9b0b31b926ba48ccbc4c15c9adc556267bd555b
4
- data.tar.gz: 7fc5beb8ff953064bf7360bbc584fb3d770b53cc
3
+ metadata.gz: 2c279b6acf6f388f798beaa929897eb6288569fb
4
+ data.tar.gz: e7e7c62299739c5e66b87bfcd9b43559764ba0c2
5
5
  SHA512:
6
- metadata.gz: f7229f88f06e7fa7f6b26c47c41289af9f915483a7fca40bd551a2e520e5c4c8c4efa416b9be3e10450a7723aadd335ce11331d584797adc47d607eb71b39658
7
- data.tar.gz: 4b9fb0ff3db1a8fd11ccdf6643e27c6c15c6a8154a5333379a8d432b69cc22da21cd99ecdee9cbe51b79a56b03e8e8bc1762848736d81b5b454241f9f14853c4
6
+ metadata.gz: c259fdcfe8a3bab4f69ca230d2855f468b682eb7b5ef2657b8858f199bfaf5ac4a7d81b65afc9dea34f47e6e2dea825392d86750440689101713425d5ad6a006
7
+ data.tar.gz: d7ad39098c7f1573b31a0f29e1da22f36120380175121a7ffd416f1d248d45e1e1d2f12980735d89c7031ed6f7a73a03e92d3476f7469f0c73ab71e895b11de3
data/README.md CHANGED
@@ -16,15 +16,10 @@
16
16
  * [Quick Start](#quick-start)
17
17
  * [Details](#details)
18
18
  * [FAQ](#faq)
19
+ * [Comparisons](#comparisons)
19
20
 
20
21
  ## Motivation
21
- Whenever your application manages users, you will inevitably need to handle email confirmation, password reset, user invitations, and other authentication flows. While not too complicated, they are sort of annoying to implement and some great libraries have our backs. [Devise][devise] and [Sorcery][sorcery] are great options that we have used in the past, but we found ourselves wanting both a little less and a little more.
22
-
23
- ### Devise
24
- [Devise][devise] is an amazing gem! It is perfect when you want an all-in-one solution that handles user authentication and associated flows for your Rails/ERB app. Everything is in the box, including the routes, controllers, views, and even mailers to handle user auth. But we often use Rails as an API and/or wanted more control over all those pieces and it became difficult to peel back all the layers to just to confirm a user's email.
25
-
26
- ### Sorcery
27
- [Sorcery][sorcery] is great and we highly recommend it. It is closer to what we wanted but still was a bit more than we needed and even the < 20 methods seemed like more than necessary.
22
+ Whenever your application manages users, you will inevitably need to handle email confirmation, password reset, user invitations, and other authentication flows. While not too complicated, they are sort of annoying to implement and some great libraries have our backs. [Devise][devise] and [Sorcery][sorcery] are great options that we have used in the past, but we found ourselves wanting both a little less and a little more. See our more detailed thoughts on these options [below](#comparisons).
28
23
 
29
24
  ### User Authentication Flows
30
25
  Email confirmation, password reset, user invitations are all variations of the same process:
@@ -52,7 +47,7 @@ Does not take over your app, minimal magic, and only if you want it. Token Maste
52
47
  Works for APIs, ERB apps and everything in between.
53
48
 
54
49
  ### Simple
55
- Only 6 methods and you may not even use them all!
50
+ Only 5 methods and you may not even use them all!
56
51
 
57
52
  ### Helpful errors
58
53
  We take the approach of raising an error whenever anything unexpected happens and provide a specific error with a helpful message to aid your debugging and testing experience.
@@ -300,6 +295,16 @@ Bug reports and pull requests are welcome on GitHub at https://github.com/Launch
300
295
 
301
296
  The gem is available as open source under the terms of the [MIT License](http://opensource.org/licenses/MIT).
302
297
 
298
+ ---------------------------
299
+
300
+ ## Comparisons
301
+
302
+ ### Devise
303
+ [Devise][devise] is an amazing gem! It is perfect when you want an all-in-one solution that handles user authentication and associated flows for your Rails/ERB app. Everything is in the box, including the routes, controllers, views, and even mailers to handle user auth. But we often use Rails as an API and/or wanted more control over all those pieces and it became difficult to peel back all the layers to just to confirm a user's email.
304
+
305
+ ### Sorcery
306
+ [Sorcery][sorcery] is great and we highly recommend it. It is closer to what we wanted but still was a bit more than we needed and even the < 20 methods seemed like more than necessary.
307
+
303
308
  <!-- Links -->
304
309
  [devise]: https://github.com/plataformatec/devise
305
310
  [sorcery]: https://github.com/Sorcery/sorcery
@@ -1,4 +1,4 @@
1
1
  module TokenMaster
2
2
  # Current version of TokenMaster
3
- VERSION = '0.1.3'.freeze
3
+ VERSION = '1.0.0'.freeze
4
4
  end
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: token_master
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.1.3
4
+ version: 1.0.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - Dave Corwin
@@ -9,7 +9,7 @@ authors:
9
9
  autorequire:
10
10
  bindir: bin
11
11
  cert_chain: []
12
- date: 2017-04-26 00:00:00.000000000 Z
12
+ date: 2017-05-08 00:00:00.000000000 Z
13
13
  dependencies:
14
14
  - !ruby/object:Gem::Dependency
15
15
  name: rake