Thor VS Devise Token Auth

Ruby has always been a great general-purpose scripting language and is often used to create command-line utilities. Many of these use the excellent Thor gem to parse command-line options, but there's no escaping one fact: command-line utilities just aren't interesting. Never have been, never will be.

All public methods in the generator will be called one after the other. Private methods will not be called but are available in your public methods like regular Ruby classes.

ruby: http://whatisthor.com

I will add that if you want to develop a CLI tool that gives you various commands that you can run, I would have a look at something like thor to keep it organised and documented. But this is completely unnecessary as a first step - you can simply create a Ruby file that does a thing you want and invoke it directly.

Not to be confused with generator functions (which you might be familiar with from Python or Javascript), Rails generators are custom Thor commands that focus on, well, generating things.

I wanted to provide a command-line interface for the user that was easy to use, and I also wanted to provide the flexibility with the options used to render the animation. After looking around online I found that Thor was a good tool to utilize. It allowed me to easily create a number of options that make this program much more versatile. An example below shows how a user can select which folder the source images are in, as well as what the background and foreground colors should be:

I've used Thor a lot, but it's kind of terrible. It uses a custom non-POSIX-compliant option parser (ex: method_option :list, type: :array -> --list one two three, where as the POSIX way is --list one,two,three or --item one -- item two --item three) and will not error on unknown options or exit with -1 when not enough args are given. If you want a better CLI library, checkout dry-rb, command_kit, or cmdparse.

And Thor might be worth looking at if you have complex scripts: https://github.com/erikhuda/thor

I have a React single page application using React Router that hooks into a Rails 5 API. The Rails application uses devise_token_auth for authentication. I've successfully created an authentication process that stores the user state in a Redux store on the client side.

Did you send an authorization header with your api call? The error is pretty clear — the request is unauthorized. Devise is expecting session cookies, but your api should use tokens. https://github.com/lynndylanhurley/devise_token_auth

I mentioned Identity in my first comment. I've never found it as simple as Devise though - especially in an API only setting.

With Devise there's a third-party Gem you can use called devise_token_auth which deals with everything automatically.

https://github.com/lynndylanhurley/devise_token_auth

redux-token-auth is a great library. What it mainly does is it provides a plug and play auth implementation functionality for ruby on rails based APIs which implement popular devise_token_auth for auth handling.

have you looked at https://github.com/waiting-for-dev/devise-jwt or https://github.com/lynndylanhurley/devise_token_auth

I'd prefer to have a standalone rails API and a react client separately, but that's not mandatory. I discovered a gem called devise_token_auth and it didn't seem to have refresh tokens but it refreshed the tokens on every request anyway so I was pretty happy with it.

As a side note, also check out devise_token_auth here