Last active
August 25, 2023 21:11
-
-
Save Caffe1neAdd1ct/ea28bb49baaea86c203407629b442681 to your computer and use it in GitHub Desktop.
Installation of MailHog on CentOS 7
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
## Install packages | |
sudo yum install wget curl vim epel-release | |
sudo yum install daemonize.x86_64 | |
## Install mailhog | |
wget https://github.com/mailhog/MailHog/releases/download/v0.2.0/MailHog_linux_amd64 | |
sudo chmod +x MailHog_linux_amd64 | |
sudo chown root:root MailHog_linux_amd64 | |
sudo mv MailHog_linux_amd64 /usr/sbin/mailhog | |
## Install mailhog initd service | |
wget https://raw.githubusercontent.com/geerlingguy/ansible-role-mailhog/master/templates/mailhog.init.j2 | |
sudo chown root:root mailhog.init.j2 | |
sudo chmod +x mailhog.init.j2 | |
sudo mv mailhog.init.j2 /etc/init.d/mailhog | |
### Fix the paths in the mailhog init.d file | |
sudo vim /etc/init.d/mailhog | |
## Start mailhog | |
sudo chkconfig mailhog on | |
sudo service mailhog start |
I wouldn't install the v7 rpm.. most likely that would end badly unless the
package doesn't rely on anything compiled for that version then it may work
(not worth the hassle).
You could try
https://centos.pkgs.org/8/okey-x86_64/daemonize-1.7.8-1.el8.x86_64.rpm.html but
that is from a 3rd party repo so you'd need to check who and if you trust
them.
Alternatively systemd may well have something to replace this by now.
…On Fri, Jul 17, 2020 at 3:37 PM Ian Sebryk ***@***.***> wrote:
***@***.**** commented on this gist.
------------------------------
yes, i saw that this was done before v8. i just wanted you to know that it
wasn't working for current CentOS release. the problem, as i mentioned, is
that the yum install daemonize.x86_64 fails. there is no such beast in
the v8 repos. and given all the changes in v8, i wasn't confident that
manually adding the rpm from v7 would fix the problem without creating more.
if this is something you can easily fix, i'd be most grateful. if there's
something i can easily do on my end, i'm equally open to that as well.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://gist.github.com/ea28bb49baaea86c203407629b442681#gistcomment-3381252>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAKEBZGBRV7MQRGAIWRIPPLR4BO4FANCNFSM4O4ZGZMQ>
.
Thinking something like the following may work: https://tuttlem.github.io/2018/02/03/create-a-systemd-daemon.html
oooh. nice find! i'll give that a whirl in the next day or two and keep you posted. thank you. :)
if this is something you can easily fix, i'd be most grateful. if there's something i can easily do on my end, i'm equally open to that as well.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
yes, i saw that this was done before v8. i just wanted you to know that it wasn't working for current CentOS release. the problem, as i mentioned, is that the
yum install daemonize.x86_64
fails. there is no such beast in the v8 repos. and given all the changes in v8, i wasn't confident that manually adding the rpm from v7 would fix the problem without creating more.if this is something you can easily fix, i'd be most grateful. if there's something i can easily do on my end, i'm equally open to that as well.