-
Notifications
You must be signed in to change notification settings - Fork 583
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MailCatcher UI not working in 0.10.0 (when installed via homebrew) #560
Comments
Were you able to find a solution? (It's happening to me as well) |
Nope. Haven't ever written a line of Ruby, so don't really know how/where the headers are set. I'd hope/think that for anyone more familiar with Ruby and/or MailCatcher this'd be quite an easy fix. |
Same issue when installed via Homebrew for version 0.10.0 |
@joshualip-plaudit @kilis, my current workaround is to just go to Wasn't able to install version |
Seems like my initial report was incorrect and the |
Ah, interesting. Through the tap? That hasn’t been updated in a very long time. |
Oh, there’s an official formula now! but it’s missing the step that compiles assets. That’s the issue. |
Without this step the user interface does not function because the javascript and stylesheets are not compiled or included, so cannot be served to browsers. See sj26/mailcatcher#560
Seems like the |
Yeah. The formula is broken, but I don’t install with homebrew and don’t know how to fix it. Please help if you know how! 🙏 |
@sj26 I opened a discussion on the homebrew github page to discuss the proper way to fix the homebrew formula. tldr; it seems like the easiest path forward would be to add a Gemfile.lock to the mailcatcher repo. Then the formula can simply install the released gem version from rubygems. Any particular feelings about checking in a Gemfile.lock going forward? It seems kind of pointless to me, other than to satisfy the homebrew folks. Unfortunately it lightens the burden on maintaining the homebrew formula by shifting the burden to the mailcatcher repo. |
@sj26 any thoughts on the above? |
Somebody please fix this :) |
I don’t want to add a Gemfile.lock to mailcatcher. That’s an anti pattern for gems. Mailcatcher works with a range of versions. It pushes additional maintenance burden into this repo. Resolving a set of compatible software versions is the job of the package manager, imho. |
Environment:
OS: macOS Sonoma 14.4.1
Ruby: 3.3.2
MailCatcher: 0.10.0
Browser: Google Chrome (125.0.6422.114) and Mozilla Firefox (126.0.1)
The
.js
and.css
files from/assets
are resolving with an incorrectcontent-type
oftext/html
, which prevents browsers from executing them.This issue was not present in the
0.9.0
version of MailCatcher.The text was updated successfully, but these errors were encountered: