dev3 ·
Which settings do I need to change in DEV3 Palletra (payments, email, scheduled jobs) before it works for real customers? Is anything simulated by default?
#configuration#b2b-wholesale#wholesale-ordering#price-lists#credit-terms
0
DEV3 Developer Forum
How do I configure payments, email and cron for DEV3 Palletra?
Ask a question
Every post is reviewed first. Usually reviewed within 24 hours.
1 reply
dev3 · Accepted answer
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 settings exist in .env.example and in Settings. 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. The simulated gateway captures card payments at once and only from the API and portal.
Cron and queue
* * * * * cd /path/to/palletra && php artisan schedule:run >> /dev/null 2>&1The scheduler runs palletra:jobs tasks: credit-review (hourly, releases held orders that now fit), orders (every 15 minutes: internal approvals and unpaid prepaid orders that ran out), ar-age (daily, marks overdue invoices and sends dunning), quotes (daily expiry), docs (tax-exempt document warnings) and ar-check (daily ledger check). Without the cron entry, held orders never release and invoices never become overdue.
Queues use QUEUE_CONNECTION=sync in .env.example, so nothing else has to run. On a busy site you can switch to the database queue and run a worker under Supervisor or systemd.
MAIL_MAILER=log writes mail to the log. Set a real mailer in .env or in Settings before launch.
0