devise_jwt_controllers 0.1.2 → 0.1.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/Gemfile.lock +2 -2
- data/README.md +13 -0
- data/lib/devise/jwt/controllers/version.rb +1 -1
- data/lib/devise/jwt/overrides/devise.rb +1 -0
- metadata +2 -2
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 2173d91050f840640921e7e37a8c050f2fdfac0cd72ce05dd040886e90f363c7
|
|
4
|
+
data.tar.gz: 7cdfe513478817036a2f54f812935fae71f33ed3b95c3001bf5ce891b754b8d6
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 939956bd356bce7160db1ea3387acab3d6b1003c6fc42b1b20b5166530310a07358de567ca128cd5792bc0ef90e19ce940a3c8be2e306bd6fdc0202132880165
|
|
7
|
+
data.tar.gz: 1e52ad199aa3492a38d1f41cd15762d8c37e6ef592585b594f9a79950456796986e610f986b12b6b87d23a77818c2ea0b7af5142e4b7d7acc7eedc006fb249f3
|
data/Gemfile.lock
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
PATH
|
|
2
2
|
remote: .
|
|
3
3
|
specs:
|
|
4
|
-
devise_jwt_controllers (0.1.
|
|
4
|
+
devise_jwt_controllers (0.1.3)
|
|
5
5
|
devise (~> 4.7.1)
|
|
6
6
|
devise-jwt (~> 0.6.0)
|
|
7
7
|
rails (>= 5.2.0, < 6.1)
|
|
@@ -85,7 +85,7 @@ GEM
|
|
|
85
85
|
docile (1.3.2)
|
|
86
86
|
dry-auto_inject (0.6.1)
|
|
87
87
|
dry-container (>= 0.3.4)
|
|
88
|
-
dry-configurable (0.
|
|
88
|
+
dry-configurable (0.9.0)
|
|
89
89
|
concurrent-ruby (~> 1.0)
|
|
90
90
|
dry-core (~> 0.4, >= 0.4.7)
|
|
91
91
|
dry-container (0.7.2)
|
data/README.md
CHANGED
|
@@ -28,6 +28,19 @@ You then just replace your `devise_for` in `config/routes.rb` with `devise_jwt_f
|
|
|
28
28
|
|
|
29
29
|
`devise_jwt_for` accepts the same arguments as `devise_for`, and configurations.
|
|
30
30
|
|
|
31
|
+
If you are only planning to use it as an API only, remember to configure devise to respond only to JSON:
|
|
32
|
+
|
|
33
|
+
|
|
34
|
+
In your `config/initializers/devise.rb` add:
|
|
35
|
+
|
|
36
|
+
```rb
|
|
37
|
+
config.jwt do |jwt|
|
|
38
|
+
jwt.secret = 'Some secret key'
|
|
39
|
+
end
|
|
40
|
+
|
|
41
|
+
config.navigational_formats = %i[json]
|
|
42
|
+
```
|
|
43
|
+
|
|
31
44
|
## Development
|
|
32
45
|
|
|
33
46
|
After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake spec` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
|
metadata
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: devise_jwt_controllers
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 0.1.
|
|
4
|
+
version: 0.1.3
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- Ramiro Rojo
|
|
@@ -9,7 +9,7 @@ authors:
|
|
|
9
9
|
autorequire:
|
|
10
10
|
bindir: exe
|
|
11
11
|
cert_chain: []
|
|
12
|
-
date: 2019-11-
|
|
12
|
+
date: 2019-11-19 00:00:00.000000000 Z
|
|
13
13
|
dependencies:
|
|
14
14
|
- !ruby/object:Gem::Dependency
|
|
15
15
|
name: rails
|