-
-
Save Caffe1neAdd1ct/ea28bb49baaea86c203407629b442681 to your computer and use it in GitHub Desktop.
## 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 |
@richardudovich thanks, fixed my notes above 👍
this doesn't work for CentOS 8. daemonize isn't in the epel-release rpm for it. it's only in the one for CentOS 7. might want to update this script, if it can still work for 8.
@iansebryk this was put together before CentOS 8 was released (2016), I'll update the title to specify the version.
When trying this on CentOS 8 is there any particular part you got stuck on or any specific errors?
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.
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.
I had to change #! /bin/sh to #!/bin/sh for it to work correctly