laravel-queueable-action
fortify
Our great sponsors
laravel-queueable-action | fortify | |
---|---|---|
2 | 5 | |
615 | 1,540 | |
1.3% | 0.8% | |
3.8 | 7.4 | |
2 months ago | 2 days ago | |
PHP | PHP | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
laravel-queueable-action
-
Actions vs Jobs
These: https://github.com/spatie/laravel-queueable-action
-
Refactoring #2: From controllers to actions
As an extra, one could also work with Spatie's Actions package to make them queueable, or even the full-fledged Laravel Actions package. We kept it simple for now using Plain Old Objects in PHP (POOP).
fortify
-
Actions vs Jobs
I mean things like this: https://github.com/laravel/fortify/tree/1.x/src/Actions and this: https://stitcher.io/blog/laravel-queueable-actions
-
Time-based Laravel OTP Login
The main difference between my approach and theirs is that they save the code in the database while I rely on the same logic as Laravel Fortify to generate a Time-based One-time Password (TOTP) algorithm specified in RFC 6238. This is therefore not an option if your application does not use Laravel Fortify. I do not claim to offer the best solution and leaves the judgement to you the reader.
-
Laravel Fortify : Implement 2FA in a way that won't let users lock themselves out
That's really nice because it's an essential feature for any application that need decent security, and I wouldn't know where to start if I had to implement it from scratch. But as of now it has one major limitation : If you implement it by following the documentation to the letter, there's a good chance that your users will end up locked out of your app when they try to enable it. The issue is described in detail here, but it boils down to the fact that Fortify won't ask for the user to enter a code to confirm that they successfully installed the app and scanned the QR code, so if they activate 2FA and then fail to add your site to Google Authenticator (or their computer crashes or something), they wont be able to log into your site ever again.
-
Updating Laravel 8 User profile information using bootstrap livewire and fortify
To find out more about laravel fortify features you can go the the github respository Fortify and for livewire documentation you can go to livewire
-
Using Laravel Fortify to restore laravel/ui functionality
Fortify includes an interesting email verify feature; if you're interested you can take a look on the package documentation
What are some alternatives?
laravel-actions - ⚡️ Laravel components that take care of one specific task
laravel-fortify-demo - Demo of Laravel authentication using Fortify
laravel-workflow - Durable workflow engine that allows users to track job status, orchestrate microservices and write long running persistent distributed workflows in PHP powered by Laravel Queues. Inspired by Temporal and Azure Durable Functions.
laravel-2fa - An example implementation of Laravel Fortify Two Factor Authentication
openlittermap-web - https://opengeospatialdata.springeropen.com/articles/10.1186/s40965-018-0050-y
breeze - Minimal Laravel authentication scaffolding with Blade, Vue, or React + Tailwind.
mvea - MVEA Architectural Pattern : Model View Endpoint Action
lasso-ci-cd - Laravel CI/CD pipeline using Lasso and GitHub Actions.
lara8auth - This is a simple auth starter setup for laravel 8 projects using bootstrap and laravel fortify
importDevTo - GitHub Action to import markdown posts from a Dev.to user
Laravel-Phone - Phone number functionality for Laravel