Self‐Hosting without SMTP Email Server

If you want to self-host Wapy.dev without setting up a full SMTP server, you can use Mailpit for a local SMTP server and a web UI to view emails.

This document outlines how to set up Mailpit via Docker and configure your app (e.g., Wapy.dev) to use it as a development/test email server.

For more information, refer to the Mailpit documentation.

🧠 Note: Do not use Mailpit in production. It is designed for development and testing only.

Install Mailpit via Docker

Run the following command to start Mailpit via Docker:

docker run -d --restart unless-stopped --name=wapydev-mailpit -p 8025:8025 -p 1025:1025 axllent/mailpit

As an alternative, you can use Docker Compose to run Mailpit. Add the following content to docker-compose.yml file:

  mailpit:
    container_name: wapydev-mailpit
    image: axllent/mailpit
    restart: unless-stopped
    ports:
      - 8025:8025
      - 1025:1025

This will:

• Start Mailpit docker container in the background.
• Expose port 1025 for SMTP and 8025 for the web interface.

Update .env Configuration

Update your .env file with the following values:

# Email settings
# Email server configuration settings
EMAIL_SERVER_USER=dev
EMAIL_SERVER_PASSWORD=dev
EMAIL_SERVER_HOST=wapydev-mailpit
EMAIL_SERVER_PORT=1025

PS: Make sure to replace wapydev-mailpit with the actual hostname or IP address of your Mailpit container if it's not running on the same host as Wapy.dev. If you are using Docker Compose, you can use the service name wapydev-mailpit as the host.

Viewing Emails

Open the Mailpit web UI in your browser:

http://localhost:8025

You’ll see all emails sent through the SMTP server here, including verification codes, password reset links, etc.