Which settings do I need to change in DEV3 Odolane (payments, email, scheduled jobs) before it works for real customers? Is anything simulated by default?
#configuration#vehicle-rental#car-rental-script#fleet-management#one-way-rental
DEV3 Developer Forum
Every post is reviewed first. Usually reviewed within 24 hours.
Which settings do I need to change in DEV3 Odolane (payments, email, scheduled jobs) before it works for real customers? Is anything simulated by default?
#configuration#vehicle-rental#car-rental-script#fleet-management#one-way-rental
Payments, location and push
The default is the simulated gateway, so booking and paying work without keys. Stripe, Razorpay and PayPal drivers are included but were not run against real accounts. The security deposit is a real second charge that is refunded after check-in; there is no pre-authorisation. A card refund that keeps failing for about an hour is credited to the wallet instead. Stripe refunds have no idempotency key yet, so before you take real card payments review how retried refunds are handled. The staff app's live check was at API level. SMS and push are not wired in.
Cron
* * * * * php /path/to/odolane/artisan schedule:run >> /dev/null 2>&1
The scheduler runs odolane:tick, a safety net that sweeps idle records, retries card refunds and settles late payments. Deadlines are enforced whenever a record is read, so the cron is optional for correctness, but keep it for refunds. php artisan odolane:check reconciles stock events, deposits held and every wallet.
Languages
English throughout. The public site and both apps also include Arabic with right-to-left layout.