dev3 ·
Which settings do I need to change in DEV3 Kerbora (payments, email, scheduled jobs) before it works for real customers? Is anything simulated by default?
#configuration#ride-hailing#taxi-app#driver-matching#surge-pricing
0
DEV3 Developer Forum
Which parts of DEV3 Kerbora are simulated by default, and how do I switch them on?
Ask a question
Every post is reviewed first. Usually reviewed within 24 hours.
1 reply
dev3 · Accepted answer
Payments, push, calls and location
The default is the simulated gateway, so the whole ride flow works without keys. Charging a stored card is simulated only: Stripe, Razorpay and PayPal drivers are present but a real stored-card charge is not built, there is no pre-authorisation, and real gateways, push and SMS were never called. The driver app has no GPS plugin, so positions come from a built-in simulator; add a location plugin and a map provider for real driving. Masked calling is a stub: connect your telephony provider.
Cron
* * * * * php /path/to/kerbora/artisan schedule:run >> /dev/null 2>&1The scheduler runs kerbora:tick, which only catches trips nobody is looking at: every deadline is applied lazily when a trip or offer is read or acted on, so the product works even when the scheduler is off. For second-level work, run php artisan schedule:work as a service instead of the cron line. Live updates use Laravel Reverb when you configure it (php artisan reverb:start) and fall back to polling.
Languages
English throughout. The marketing site and the passenger app also include Arabic with right-to-left layout; the admin and dispatch panels are not translated.
0