Its seems that you can run https://sendy.co on Siteground’s Cloud service. Previously the cron and CPU restrictions from Siteground made sendy difficult to run.
I have moved my installation of sendy from an AWS EC2 tiny instance to my newly upgraded (and 20% more expensive) cloud service on Siteground.
I love Siteground, and have been with them for over 10 years. Everything they do is to make their service better for their customers. Not so excited about how much they now charge for their cloud service though. That being said, I do get 4 CPUs, 8 GB RAM, 40 GB SSD which is not too shabby.
Anyway here is what needed to be configured. I created a new subdomain, transferred across the mysql database, installed sendy and configured the cron scripts.
Siteground cron configuration
The cron configuration is located under DEVS in the beautiful new SG SiteTools.
To make the sendy scripts run every 5 minutes, you can paste the cron schedule string “*/5 * * * *” into the form and it senses automatically that this means every 5 minutes. Just set the Interval to Set Manually.
Whilst I could get 50 emails a second from the N. Virginia located EC2.tiny, the SG server in Iowa is slower to send to Amazon’s SES servers, more like 10 per second effective send rate. Whilst this is a lot slower, it is more convenient to have all my services in one location.
Proving it worked
I’m still proving that the emails were actually delivered. Sendy says that 5804 emails were sent to the SES servers, but my SES status page says only 1958 emails have been sent in the last 24 hours. I seems to be missing a few of my honeypot emails as well.
Update February 2022
Siteground have since migrated to Google Cloud Services to host all of their infrastructure, so the path names have changed and usernames to login with ssh.
I seem to be able to maintain a solid 20 emails per second with the SG cloud server which is enough for me.
So overall it is good news that send and siteground look to be ok.