dev3 ·
Which settings do I need to change in DEV3 Hagglo (payments, email, scheduled jobs) before it works for real customers? Is anything simulated by default?
#configuration#classifieds#classified-ads#local-marketplace#buy-and-sell
0
DEV3 Developer Forum
Which parts of DEV3 Hagglo 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 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. One-time codes for app sign-in are written to the log until you configure an SMS provider.
Cron and queue
* * * * * cd /path/to/hagglo && php artisan schedule:run >> /dev/null 2>&1The scheduler runs the jobs the marketplace depends on: hagglo:expire-listings (ads past their end date), hagglo:lapse (offers and reservations that ran out), hagglo:bump (scheduled bumps), hagglo:alerts (saved-search alerts) and hagglo:housekeeping (daily clean-up). Without the cron entry, ads never expire and bumps never fire.
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