Configuring email

Some features send email — email verification and password reset both need a mailer to deliver their links. When your build includes one of these, your generated app needs to know how it sends mail.

The default: the log mailer

So a build never stops to ask for credentials, Stellify configures your app with Laravel's log mailer by default. Your app builds and runs immediately, and any email it "sends" is written to the application log (storage/logs/laravel.log) instead of being delivered.

That's perfect for development and for seeing the flow work — but no real email is sent until you configure a real mail service.

We never ask for mail credentials in the chat. Credentials belong in your app's environment, not in a conversation — so you set them yourself, in the place Laravel reads them from.

Sending real email

Pick a mail service (SMTP, Mailgun, Postmark, Amazon SES, Resend, …) and set its values in your exported app's .env file. For SMTP that's:

MAIL_MAILER=smtp
MAIL_HOST=smtp.your-provider.com
MAIL_PORT=587
MAIL_USERNAME=your-username
MAIL_PASSWORD=your-password
MAIL_FROM_ADDRESS="hello@yourdomain.com"
MAIL_FROM_NAME="Your App"

These map straight onto Laravel's mail configuration in config/mail.php, which your exported app already ships. Switch MAIL_MAILER to mailgun, postmark, ses, or resend and fill the matching keys to use those services instead.

Where the values live

• In your exported app — set them in .env (above). This is the usual path.
• On a managed host (e.g. Laravel Cloud) — set the same keys as environment variables in your host's dashboard, so secrets never sit in a file.

Learn more

Laravel's own mail guide covers every driver, queued sending, and local testing tools like Mailpit: https://laravel.com/docs/mail.