GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
Already on GitHub? Sign in to your account
Added db persistance with available cmd line option db-path for db file.
Added questionable UI message handling before quiting mailcatcher for consistency, because for file db we wont lose our messages.
I kinda have a rewrite in the wings that I was planning to implement this with... I do like the approach but stay tuned.
would supporting alternate database backends be one method of implementing persistence?
I'm currently using MailCatcher in "single user development environments": low activity, nightly database resets, regular daemon restarts. I'd like to deploy MailCatcher to our "integration environment", but the activity level there is much much higher. I don't want to restart MailCatcher every day so the in-memory SQLite DB doesn't balloon to an insane size. having MailCatcher write to MySQL solves persistence and long-term memory usage.
Would love to see persistence make it into master 👍
+1 SQLite to disk would suffice w/configuration option to expire after x days or y messages.