mirror of
https://github.com/axllent/mailpit.git
synced 2026-04-26 08:45:54 +03:00
[GH-ISSUE #200] White screen when visiting the Web UI #130
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#130
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 @nkosi23 on GitHub (Oct 29, 2023).
Original GitHub issue: https://github.com/axllent/mailpit/issues/200
Hello,
I am new to mailpit and have just installed it using
go install github.com/axllent/mailpit@latest. While mailpit is apparently successfully launched:Visiting the web page gives me a blank page and I can see the following messages in dev tools:
I apparently get 404 errors for these two files. The HTML of the page is:
There is nothing fancy in my setup (no reverse proxy etc...) I am just launching the binary.
@axllent commented on GitHub (Oct 29, 2023):
Hi there. You cannot install Mailpit in this way because it doesn't come bundled with precompiled CSS & J's files. Please refer to the documentation if you wish to compile it yourself.
@nkosi23 commented on GitHub (Oct 29, 2023):
Wow this fixes the issue, thanks a lot!
But I am a bit confused then, since everything is bundled in a single executable file and since taking a look at the source I can see that the file system used by the webserver is a virtual one, why aren't the CSS & JS included when mailpit is installed using
go install? Would it be feasible to create a go package containing the pre-built assets so that go install is able to include everything?Anyway, just to provide some context, I came across mailhog this morning and quickly noticed that people were recommending mailpit as a near drop-in replacement, so I naively assumed that it would support the same install process (which is quite neat in my opinion, but extracting a binary is easy enough to be fair).
Thanks a lot for this tool, mailpit looks like an outstanding tool that will greatly improve what used to be a rudimentary workflow as far as my email-related development tasks were concerned!
@axllent commented on GitHub (Oct 29, 2023):
@nkosi23 Good questions. The pre-compiled binaries do include everything including the "virtual" filesystem used by the web UI (bundled JS, CSS, images etc), but the source code does not include the compiled assets (just the source files to build these). The reason for this is simple: as I'm sure you can image, the precompiled CSS & JavaScript is quite large (relatively speaking). If the compiled versions were bundled and I was to make a small change to either of those, the entire compiled files would be checked back into git each time (not just the line or character change as they are minified, so everything is on a single line). This would lead to a much bigger source repository filled with tonnes of irrelevant historical data.
Anyway, this is the path I chose, and while that does mean that
go install...doesn't work, I have provided multiple ways to install a fully working version, and instructions for those wanting to compile it (all) from source.I hope that makes sense?
@nkosi23 commented on GitHub (Oct 29, 2023):
This makes absolute sense, thanks a lot for taking the time to share these insights with me