MailCatcher VS the_silver_searcher

hey HN, I recently published an article going deep into email previewing (in Ruby on Rails, but I think it's relevant beyond Rails).

MailCatcher (https://github.com/sj26/mailcatcher) and MailHog (https://github.com/mailhog/MailHog) are super handy and easy to run locally. Both spin up an SMTP server which you can direct mail to, and give you a nice web interface to browse mail and preview it.

Happy to answer any question! thanks, harrison

A couple others

* Mail Catcher https://mailcatcher.me/

Useful. Seems very similar to MailCatcher, but not depending on Ruby is always a plus.

I just upgraded to Alpine Linux 3.16.1 This is an important upgrade as it fixes 2 major issues: - busybox CVE-2022-30065 - openssl CVE-2022-2097 Related information: Mailcatcher as a docker image using Alpine Linux 3.16.1: https://hub.docker.com/r/stpaquet/alpinemailcatcher Github repo: https://github.com/spaquet/docker-alpine-mailcatcher Mailcatcher: https://mailcatcher.me

Mailcatcher: https://mailcatcher.me

Mailhog sounds a lot like mailcatcher

I would install https://mailcatcher.me and see if that local smtp works.

Useful links: Mailcatcher homepage: mailcatcher.me Dockerfile and Docker Compose: https://github.com/spaquet/docker-alpine-mailcatcher Dockerhub: https://hub.docker.com/r/stpaquet/alpinemailcatcher

I can run MailCatcher or MailHog or Postfix or Sendmail or any number of other solutions, but there's not any other linux sysadmins here so something with an easy gui setup would be convenient so others can poke around if needed.

View on GitHub

If you have trouble finding it among the other stuff happening in the server log, well, so do I! I recommend learning how to programmatically search through your terminal output. Providing a universal method for this is challenging because various tools and terminal emulators implement this functionality differently. Another option would be to use tools like grep or the_silver_searcher (a favorite of mine) to search the file where your dev logs are written to. This file is located at log/development.log in a Rails project.

Some of the examples below use ag, but could just as well use grep or equivalent.

Why guess when [there are installation instructions for various platforms on the README](https://github.com/ggreer/the_silver_searcher#installing)?

Also, although it may not be easy to remember, is this really a problem in practice given the installation count in most contexts is one? If there's a context where it's installed regularly, that's a one-time addition to an install script, Dockerfile, etc. in my experience. Do you have a situation that isn't amenable to that?

The kernel changes a lot, so the books would get outdated quickly. But you can find simple / similar drivers, and read the code. Usually there are some documentation / comments on the headers before the function declarations. The Elixir and the Silver Searcher will help a lot.

URL 🔗 : https://github.com/ggreer/the_silver_searcher

My "vim" way of finding all the places where a function is being used: using visual mode, marking the function, and passing it to :Ag (silversearcher) The problem with this is that it is not 100% accurate, since it will just look for things with the same name, so I was thinking about using the LSP to make things more robust.

We're fans of ag, The Silver Searcher.

Helm-ag is an interface to the ag, silver-searcher, so check the docs for ag. For example, ag automatically ignore some files if there is a .gitignore with some file patterns, or you could use .agignore.