Hi Arial, sorry, that part is not relevant to the blog post - it was taken from a different approach ( like having many stores to deal with ) - and I've decided to show the simplest method but if you want I can add a section on how I handle the connections with multiple stores.

Hi japet saberon , I am happy that my post is helping you. Let me explain a bit better. The not_authorized in this case is a localization key, and it should be entered in the resource\lang\en\auth.php , you can read more about localization directly from the laravel website: laravel.com/docs/localization - but let me know if you still struggle. About the auth.guest middleware, as mentioned on my post, you should put it in $middleware property of your app/Http/Kernel.php class. Let me know if you need more help :)

I like the idea of learning how a programming language works. As today, almost every programmer is focused on getting the job done, but not how. We follow best practices, but we are still far from what you mentioned. Knowing how the browser interprets the code, will impact our skills and will make us think what function is better and so which should we use when interacting with data, like for() and forEach() for example. I would like to know when and if your book will be released :)

After considerable research, I found this https://blog.jetbrains.com/phpstorm/2017/01/git-questions-how-do-i-switch-branches-without-losing-my-work , which doesn't completely fix the problem, but it helps a lot. It is going to be a small solution for the moment. I can have multiple features, such as: Make the background blue Make the text red Make the title bigger I can compile and shelve the code changes (included the compiled app.js) of each feature, then switch between different shelves as I work on them. Once I am happy with the result, merge it in the staging branch for testing. Let me know what you think! :)