Which settings do I need to change in DEV3 Borrova (payments, email, scheduled jobs) before it works for real customers? Is anything simulated by default?
#configuration#rental-marketplace#equipment-rental#peer-to-peer-rental#booking-calendar
DEV3 Developer Forum
Every post is reviewed first. Usually reviewed within 24 hours.
Which settings do I need to change in DEV3 Borrova (payments, email, scheduled jobs) before it works for real customers? Is anything simulated by default?
#configuration#rental-marketplace#equipment-rental#peer-to-peer-rental#booking-calendar
Payments, push and SMS
PAYMENT_GATEWAY=simulated, PUSH_DRIVER=simulated and SMS_DRIVER=log are the defaults, so the whole site works without keys. Stripe, PayPal and Razorpay drivers are present, and you enter your keys in Settings > Payments. These drivers and the real push and SMS drivers have not been run with live accounts, so test each one in sandbox mode before you take real payments. A card booking makes two charges, the rental and the refundable deposit, and confirms only when both succeed. One-time codes for app sign-in are written to the log until you configure an SMS provider.
Cron and queue
* * * * * cd /path/to/borrova && php artisan schedule:run >> /dev/null 2>&1
The scheduler runs the jobs the marketplace depends on: borrova:expire (unpaid holds and unanswered requests, every minute), borrova:late-check (late returns and conflicts, every 15 minutes), borrova:settle (owner payments after the settlement delay, hourly), borrova:complete (returned bookings with no claim, every 10 minutes) and borrova:reveal-reviews (hourly). Without the cron entry, holds never expire, deposits are never refunded and owners are never paid.
Queues use QUEUE_CONNECTION=sync in .env.example, so nothing else has to run.
MAIL_MAILER is set in .env.example. Set a real mailer in .env or in Settings before launch, and check the mail log if nothing arrives.