Development
Managed Mail catcher on your own cluster
Catches every email a staging app tries to send and shows it in a web inbox, so a test signup cannot email a real customer.
Created inside a project, beside the apps that use it. Each project gets its own instance, storage and credentials.
01What it does
Mail catcher, run for you
Mailpit on the vendor's chart.
For development and staging projects. Bound apps get SMTP_HOST, SMTP_PORT and SMTP_FROM, which is usually all a mailer needs to point at it, and every message they send lands in a web inbox instead of a customer's.
Nothing is stored beyond the inbox, so there is no volume and no size to choose. Publish the inbox on a hostname and the whole team can read what the app sent.
02Options
What you choose
What the console asks when you create it, in the catalog's own numbers. Anything marked chosen once cannot change without creating a new instance.
- Storage
- None
- Hostname
- The inbox can be published on a domain
- Pause
- No; pause the project instead
03Binding
What your app receives
Bind it to an app and these arrive as environment variables. The values are generated once into a secret and reach the app from there, rather than as something you copy.
- SMTP_HOST
- SMTP_PORT
- SMTP_FROM
04Adding it
Add Mail catcher to a project
The same four steps as every service in the catalog.
- 01Open a project and go to Services.
- 02Pick it from the catalog and choose its options. Only the size is required; everything else has a default.
- 03Create it. Anyport installs it into the project's namespace, generates its credentials into a secret there, and tracks its health.
- 04Bind it to an app. The connection details arrive as environment variables, and rotating the credential never means editing an app.