- What is zacksmash/fortify-ui and how does it differ from Laravel Breeze or Jetstream?
- zacksmash/fortify-ui is a Laravel Fortify driven replacement for the Laravel UI package, providing Blade views and components for login, registration, password reset, email verification, and two-factor authentication. Unlike Breeze or Jetstream, which ship their own auth scaffolding stacks, this package layers a ready-made UI on top of Fortify's backend features. It fits best when your application already uses Fortify and you want prebuilt auth screens without building them from scratch. It is not a general PHP auth framework and should not replace Fortify, Breeze, or Jetstream without a deliberate auth architecture decision.
- How do I install zacksmash/fortify-ui in a Laravel application?
- Install it via Composer, then publish the package views and configuration as needed and align your Fortify routes and middleware. Because the release notes are sparse, verify PHP, Laravel, and Fortify version constraints before installing. Do the install in a non-production branch and test login, registration, password reset, email verification, and 2FA flows before deploying.
- Which Laravel, PHP, and Fortify versions are supported by zacksmash/fortify-ui v2.0.x?
- The available v2.0.2 notes do not specify an explicit compatibility matrix for Laravel, PHP, or Fortify versions. Treat compatibility as something you must confirm against your application's Composer constraints and Fortify configuration. Check the repository's composer.json and release history, and plan a regression test on a branch before adopting. If guaranteed version support matters for your team, ask the maintainer directly.
- Does zacksmash/fortify-ui include two-factor authentication views and recovery codes?
- The package adds Blade views and components covering two-factor authentication alongside login, registration, password reset, and email verification. The v2.0.2 patch specifically fixes a missing 2FA confirmation step, so the 2FA flow is actively relevant to the package. Whether recovery codes are fully covered by automated tests is not documented in the release notes, so verify that flow manually. Test 2FA enrollment, confirmation, and recovery codes in a staging environment before production rollout.
- Do I need to publish views and config after installing zacksmash/fortify-ui?
- Yes, typical Laravel package usage involves publishing views and configuration so they can be adapted to your application, though you should confirm the exact publish tags in the package documentation. Customizing published views creates upgrade drift, so keep a diff and merge plan for upstream template changes. If you do not need customization, prefer using the package views as-is to simplify future updates.
- Does zacksmash/fortify-ui override Fortify routes and controllers or only provide Blade views?
- The package is described as a UI layer for Fortify, so the expectation is that it primarily provides views and components rather than replacing Fortify's controllers. The technical assessment flags this as an open question, so confirm in the source whether any routes, middleware, or config are overridden. Before adopting, review published routes and config to understand exactly what changes in your app. Avoid mixing package views with heavily customized local auth views without a diff and merge plan.
- How do I upgrade from v2.0.1 to v2.0.2 and what changes are needed for the 2FA confirmation fix?
- Upgrade in a dedicated branch by updating the Composer constraint to v2.0.2, then run your auth regression tests. The v2.0.2 release fixes a missing 2FA confirmation step, which is security-relevant if the package is already in use. Check whether republishing views or adjusting routes and config is required, because the release notes do not state migration steps explicitly. Roll out behind a feature flag or staged deployment if the change is user-visible.
- Is zacksmash/fortify-ui safe for production authentication, and does it have automated tests?
- The package touches a security-sensitive auth surface, and the v2.0.2 2FA confirmation fix is a meaningful correction, so treat it as a security-relevant patch. Release notes do not provide explicit test evidence or a compatibility matrix, which limits confidence without further review. For production, assign an internal maintainer, define an escalation path for security patches, and add your own automated auth regression tests. Community open-source support likely has no SLA.
- Can I customize the Blade views in zacksmash/fortify-ui to match my design system?
- Yes, published Blade views and components can be adapted to your design system, localization, accessibility, and CSP requirements. The trade-off is upgrade drift: customized views may need diffing and re-merging when upstream templates change. Validate that the package's views align with your frontend stack and asset pipeline before rolling out, and keep an internal owner for view diffs.
- What are the alternatives to zacksmash/fortify-ui for Laravel authentication UI?
- Laravel Breeze and Jetstream are the most common alternatives, but they ship their own auth scaffolding stacks rather than layering on top of Fortify. Laravel UI is the package this one replaces, and it provides its own scaffolding approach. If your application already standardizes on Fortify, zacksmash/fortify-ui is a natural UI layer; otherwise, choose an alternative deliberately as part of your overall auth architecture.