Hacker News Reader

Comment by FLGMwt | Hacker News Reader

I'd pay for it even if it was just empty repo => dumb site w/ user auth. Haven't found a good concise tutorial for that.

View on HN

I plan on writing something up soon, getting my code bases in order right now. See my other comment: https://news.ycombinator.com/item?id=13155919

Hey, as a followup to this post, check this out: http://nodewebapps.com/2016/12/20/create-a-web-app-with-user...

Made it especially with you in mind. And it's free.

https://www.udemy.com/react-redux-tutorial/

Section 6 & 7 - maybe this is what you are looking for?

The tutorial you linked definitely requires a good grasp on React & Redux, I suggest starting with this course: https://www.udemy.com/react-redux/

Udemy frequently has sales on holidays and all courses are ~$15

Seconded. I'm currently muddling through a universal Javaript React starter kit and wiuld love a comprehensive guide

Are you struggling just with setup?

No, I've created a fully functioning app. Just best practices for actually deploying in the wild

User auth has definitely been the hard part for me as well on projects. I'd be interested.

> I'd pay for it even if it was just empty repo => dumb site w/ user auth

Never understood what is so hard with user auth and why people need an example of a SPA with user auth. Your server is just a web API, so just use stateless authentication.

The tutorials/instructions I've see never address the reasons for the authors' decisions, and any alternative packages or approaches that might be considered by the reader. Informing should also be a goal rather than simply providing a recipe.

The reasons for these decisions would go a long way to addressing the concerns bitdeveloper has, too.

I'll be writing up my own experience building auth for askinline.com. I don't know how to keep you in the loop other than saying to follow me on Medium or Twitter.

It's a React + Redux front end with Hapi + Sequelize backend. It uses JWTs in local storage for authentication (that decision will take some defending since it most applications should store it in a cookie) and sometimes uses single uses JWTs for things like email verification. I'm planning to write up how we do Google Login, password based signup and login including email verification and initial load decisions tree for dashboard or login page.

"most applications should store it in a cookie"

Why do you think that most application should store JWT token in the cookie? Both approaches have their pros/cons.

Cookies have several security features built in and if all you're storing is a session identifier they are generally better than a JWT from a size perspective.

This does a better job that I'm going to try for in a HN comment: http://cryto.net/~joepie91/blog/2016/06/13/stop-using-jwt-fo...

I think it's mostly because getting it wrong is a Pretty Big Deal, so people aren't sure if they can trust themselves and the scheme they came up with.

Reply on news.ycombinator.com