Which settings do I need to change in DEV3 Learnova (payments, email, scheduled jobs) before it works for real customers? Is anything simulated by default?
#configuration#lms#learning-management#online-courses#e-learning
DEV3 Developer Forum
Every post is reviewed first. Usually reviewed within 24 hours.
Which settings do I need to change in DEV3 Learnova (payments, email, scheduled jobs) before it works for real customers? Is anything simulated by default?
#configuration#lms#learning-management#online-courses#e-learning
Payments
The default gateway is Simulated: checkout shows Pay and Decline buttons and charges nothing. To take real payments, open Settings → Payments, choose Stripe, PayPal or Razorpay, set the currency and keys, and register the webhook https://your-domain/dev3/webhooks/payments/<gateway> in the gateway's dashboard. A paid order enrols the student when the webhook arrives, so check the webhook first if a student paid but isn't enrolled. Test with sandbox keys first; the PayPal and Razorpay drivers have not been run against live accounts.
Cron and queue
Add one cron entry that runs Laravel's scheduler every minute:
* * * * * cd /path/to/learnova && php artisan schedule:run >> /dev/null 2>&1
In cPanel choose Once per minute and use the full PHP path if needed. The scheduler records a heartbeat, shown in System → System health, and in demo mode resets the demo nightly. Drip unlocks don't need cron: they are worked out whenever a student opens a course.
The queue is sync by default: enrolment, certificate and announcement emails are sent during the request, with nothing to set up. On a VPS you can set QUEUE_CONNECTION=database and run php artisan queue:work --tries=3 under Supervisor for a faster interface.
Until you set up mail, outgoing email is written to the log. Open Settings → Mail, choose SMTP and enter the host, port (587 for TLS or 465 for SSL), username, password and from address. Values saved in Settings override .env.
Two-factor authentication
Every account can add a second sign-in step from its profile (avatar menu → Profile): an authenticator app (TOTP) with 8 single-use recovery codes, an emailed 6-digit code, or both. Email codes need working mail.
/admin.php artisan dev3:2fa-reset you@example.com on the server.APP_KEY, so if you change APP_KEY, reset 2FA for the affected users.