101–110 of 124 posts
I'd love to see the bill of materials for that. Its _only_ running 2 PHP instances + 2 RDS instances + EBS storage costs + S3 buckets fees + ELB fees + CloudFront fees + traffic costs.
Came here to say the same thing - I'd love to see a monthly cost on a setup that looks like this... or anything on AWS. I can run many many WP sites on a $10/month box (not AWS) with proper config tunings.
I'd love to see the bill of materials for that. Its _only_ running 2 PHP instances + 2 RDS instances + EBS storage costs + S3 buckets fees + ELB fees + CloudFront fees + traffic costs.
Came here to say the same thing - I'd love to see a monthly cost on a setup that looks like this... or anything on AWS. I can run many many WP sites on a $10/month box (not AWS) with proper config tunings.
Earlier quoted context omitted.
> Has anybody working towards serverless version of wp? I'm curious on what a "serverless version of wordpress" consists of, please enlighten us on the technical details of a serverless wordpress, sincerely. And how would you have a "serverless shopping card" too ? I'm really curious about the how it. If you're talking about a static blog generator then it already exists (Hugo,...) is this what you call serverless ?
By serverless I mean version of the wp which could use Google functions ( https://cloud.google.com/functions/ ) or Amazon Lambda ( https://aws.amazon.com/lambda/ ) or Microsoft Azure Functions ( https://azure.microsoft.com/en-us/services/functions/ ) It would provide unlimited and automatic scaling, simplified setup/architecture and we would pay only for what we use.
Earlier quoted context omitted.
Came here to say the same thing - I'd love to see a monthly cost on a setup that looks like this... or anything on AWS. I can run many many WP sites on a $10/month box (not AWS) with proper config tunings.
FYI: This post is not about your personal 2-reader a month Wordpress setup but for sites scaling to the size of TC.
The smallest production instance on AWS is about $100 a month (c4.large) for 1 core (+intel HT) + 4GB ram + a few GB of EBS volume.
The setup requires at least 4 hosts, thus that's a start price of $400 a month + the other fees (hardly 10% more :D).
It's f* insane to pay more than $400 per month to run a blog. No matter the traffic.
Earlier quoted context omitted.
FYI: This post is not about your personal 2-reader a month Wordpress setup but for sites scaling to the size of TC.
FYI: You can run a professional blog on wordpress.com for about $100 a year (highest plan) and it will take millions of visitors. The smallest production instance on AWS is about $100 a month (c4.large) for 1 core (+intel HT) + 4GB ram + a few GB of EBS volume. The setup requires at least 4 hosts, thus that's a start price of $400 a month + the other fees (hardly 10% more :D). It's f * insane to pay more than $400 pe…
>It's f* insane to pay more than $400 per month to run a blog. No matter the traffic.
This guide is spot on for WordPress on AWS. The persistent and shared EFS volume was the missing piece for running WordPress without frustrating patches. And CloudFormation is the AWS best practice. Convox has a few serious WordPress installs. The only difference is that it uses ECS so those EC2 instances can be utilized for more apps. Also you can hack on the WordPress site locally with Docker via 'convox start' htt…
Do you have anything to say about EFS and WordPress (or other PHP CMS that are basically designed for a single instance?) Latency on stat() - PHP is often a oop-monster these days with thousands of fs reads as it loads the code? (there are certainly ways to dodge that overhead though). Have you seen the filesystem stall for any reason? Any caveats with concurrent writers (such as cache/ directories or generated image…
Earlier quoted context omitted.
And avoid caching plugins. Most of them are garbage.
If you're going to add (full-page) caching, Batcache [0] is the best solution. Combined with a Memcache plugin [1], you can use this to store your page caches in AWS Elasticache. [0]: https://github.com/automattic/batcache [1]: https://github.com/tollmanz/wordpress-pecl-memcached-object-...
This is one way to do it, though I can't recommend it as the best way. The first step is building your WordPress site correctly, and for me, that starts with using trellis ( https://roots.io/trellis ) and bedrock ( https://roots.io/bedrock ). He's partially correct about S3 for media and uploads, but you want to take it one step further and use Imgix for actual image (jpeg/png) delivery because it'll do all of the tr…
This is one way to do it, though I can't recommend it as the best way. The first step is building your WordPress site correctly, and for me, that starts with using trellis ( https://roots.io/trellis ) and bedrock ( https://roots.io/bedrock ). He's partially correct about S3 for media and uploads, but you want to take it one step further and use Imgix for actual image (jpeg/png) delivery because it'll do all of the tr…
$20 a month for the DO droplet, but out of curiosity what's the monthly bandwidth bill from AWS? That's always the kicker - bandwidth from AWS is not cheap.
We are on AWS and have a pretty sophisticated Chef setup, but I want to stress that if you are a SaaS company, you do _not_ want your Wordpress install as part of your production network. By running Wordpress yourself you're taking on upgrade responsibilities, and you need to be pretty diligent in upgrading in order to avoid exploits. At minimum you should put Wordpress in its own VPC; we ended up running on Heroku instead to keep it as far as possible from our production infrastructure.
If I were setting up a new wordpress blog for a company I'd go with WPEngine if possible, if not I'd host on Heroku, and only if it needed to scale a lot would I consider hosting it myself on AWS.