- What is rayiumir/vordia used for in Laravel?
- Vordia is described as a Laravel mobile authentication package that supports multiple drivers for phone-based login and verification flows. It is intended to reduce boilerplate around mobile auth, driver selection, and related configuration. Review the README and release notes for the exact contracts and supported flows before adopting it.
- Is Vordia for mobile authentication or CRUD admin panels?
- The package description and v1.7.0 technical assessment focus on Laravel mobile authentication and SMS drivers. A supplied blurb mentions admin panels and CRUD interfaces, which may reflect a different package or a broader feature set. Confirm the actual feature set in the README before choosing Vordia for back-office CRUD.
- How do I install rayiumir/vordia with Composer?
- Install it with composer require rayiumir/vordia, then follow the package service provider and config publishing steps. In Laravel, you typically publish the config file and set driver credentials in the environment file. Confirm the required Laravel and PHP versions in composer.json before installing.
- Which Laravel versions does Vordia support?
- The package is built for Laravel, but the provided context does not list explicit framework constraints. Check the composer.json require block and the README for supported Laravel major versions. A minor driver addition such as v1.7.0 is unlikely to change framework constraints, but verify rather than assume.
- How do I configure multiple drivers in Vordia?
- Vordia supports multiple drivers, so configuration usually centers on a default driver plus per-driver credential blocks. Set the active driver in the published config or environment file and provide the required keys for that provider. Keep unused drivers unconfigured only if the package resolves them lazily; otherwise add placeholder config to avoid boot errors.
- Does Vordia support OTP-based mobile authentication?
- The package description positions Vordia as a Laravel mobile authentication package, which typically covers phone verification and OTP-style login flows. The exact OTP endpoints, expiry rules, and rate limits depend on the driver and package contracts. Check the README and driver implementations for the flows you need.
- What changed in Vordia v1.7.0?
- According to the technical assessment, v1.7.0 is a minor release whose sole change is adding a Melipayamak driver, an Iranian SMS gateway. The change is additive and follows the existing driver model if it registers through the same contract and config conventions. It should be a no-op upgrade for teams not adopting that driver.
- Is the Melipayamak driver in Vordia production ready?
- Treat it as a new additive driver and verify contract fidelity, test coverage, queueing behavior, and credential handling before production use. The assessment flags regional, sanctions, and data residency concerns for organizations with EU or US nexus. Those are governance decisions separate from code quality.
- How do I test Vordia mobile authentication in Laravel?
- Use Laravel testing tools to fake HTTP calls and assert that the correct driver receives the expected payload. Test both the selected driver and fallback behavior, and verify that queueing and retry settings behave as configured. For the Melipayamak driver, prefer a stubbed HTTP layer over live SMS sends.
- Is upgrading to Vordia 1.7.0 safe for existing Laravel apps?
- Semver-minor implies backwards compatibility, but verify the published config stub and any new keys before merging the bump. Existing consumers not using Melipayamak should see no application code changes. Run composer update in a branch and smoke-test authentication flows.