mirror of
https://github.com/axllent/mailpit.git
synced 2026-04-26 00:35:51 +03:00
[GH-ISSUE #316] Add label to differ between different instances #206
Labels
No labels
awaiting feedback
bug
docker
documentation
enhancement
github_actions
invalid
pull-request
question
stale
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/mailpit#206
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Chris53897 on GitHub (Jun 20, 2024).
Original GitHub issue: https://github.com/axllent/mailpit/issues/316
It would be great to have a label, that is displayed right to the name in the gui.
With this people can see direct, in which instance they are.
Maybe something like
MP_LABELorMP_TITLEhttps://mailpit.axllent.org/docs/install/docker/
@axllent commented on GitHub (Jun 20, 2024):
This is an interesting idea. Next to the logo won't work as there isn't enough space (specifically on mobile), but above the Inbox button probably would work.
For context, could you please explain how you're using Mailpit, specifically why there may be confusion as to which instance it is?
@Chris53897 commented on GitHub (Jun 20, 2024):
I have 3 symfony projects running with Mailpit includet locally at the same time.
They run at http://localhost:[PORT]
I can only differ them via the port.
Of course if there are e-mail in the inbox it is a bit easier.
@axllent commented on GitHub (Jun 20, 2024):
Makes sense.... I'll look into this in the coming days 👍
@axllent commented on GitHub (Jun 21, 2024):
I have added this feature, although this has not been released yet as I just released a new version 2 days ago (so I will wait a few more days so I don't annoy package maintainers... sorry).
The
--label(or envMP_LABEL) will do the following:I'll let you know when this gets released. Can you please tell me if this approach is suitable?
@Chris53897 commented on GitHub (Jun 22, 2024):
Thanks
@axllent commented on GitHub (Jun 22, 2024):
This feature has been released in v1.18.7. Please feel free to re-open this ticket if you experience any issues, and also please let me know if it solves your issue, thanks.