We do exactly this, but we keep our site code including plugins in github and the images in EFS. I would really like to see some recommendations on dealing with the Linux stat issue over NFS.
Wordpress on AWS: smooth and pain free
31–40 of 124 posts
Re: Wordpress on AWS: smooth and pain free
#32Why is anyone running WordPress anymore.? So many better options.100s if not 1,000s. The fact that you need elaborate guides to host it one of the most common hosting providers is yet another example. It's junk. Time to move on. Edit: and the down votes are why this piece of garbage lives on. Please stop trying to hide how awful WordPress is. We all know it's terrible. Just because you work on it for a living doesn't…
Can you list a few? I'm genuinely curious which ones you consider so much better.
I run https://ghost.org/ inside a Docker container and I'm quite happy with it.
Re: Wordpress on AWS: smooth and pain free
#33Earlier quoted context omitted.
Can you list a few? I'm genuinely curious which ones you consider so much better.
What your requirements? With Google rendering JavaScript any static site generator is probably going to be better. If you need crud functionality any number of hosted and open source crud providers are available. Or just use a hosted site builder. They are all better at this point.
Static site generators are just fine for personal blogs. They don't fit the bill at all when you have a group of people all writing on one blog and you need things like access controls and media file management.
Also, not sure why google rendering JavaScript would have any effect on static site generators.
Re: Wordpress on AWS: smooth and pain free
#34Earlier quoted context omitted.
Because moving an existing site to another platform is non-trivial. Sure I could figure out how to move over my theme, hundreds of posts, my menus, sidebars, hundreds of images, and all of my registered users. Or I could just stick with the existing good enough system and go do something else.
Sure, you need to support legacy software that is so junky you have no way to migrate off the platform. You're trapped in the dump. Even more reason to avoid WordPress and not get trapped in your situation.
So many ignorant statements in this comment.
Re: Wordpress on AWS: smooth and pain free
#35I do performance WP hosting and would like to try out EFS but it is not available locally yet.
What I do is use redundant RDS, ELB etc but on all the WP installs have an inhouse plugin that with any change it ioniced rsyncs that vhosts tree to all webservers and ssh's a command to them all to dump their WP cache.
It may seem hackish but the sites absolutely fly, have tried several clustered file systems but all that complexity hits reliability and speed.
Re: Wordpress on AWS: smooth and pain free
#36This 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…
I have seen some users file system calls stall due to the EFS quotas.
This was on a workload much tougher than WordPress.
I haven't run my own NFS for comparison.
I recommend reading the NFS v4 spec. AWS has all the pieces to implement the protocol as well as anyone can.
Re: Wordpress on AWS: smooth and pain free
#37In my humble opinion, WordPress is something to be surpassed, that is why it fails on being cloud-friendly. If someone makes a system as customizable and flexible as WordPress it would be a huge success.
I've been waiting on this for awhile, currently I run most sites through jekyll and for clients that need CMS options I hook them up with http://cloudcannon.com/
I've gone the WP a number of times and it's been more headaches then it's worth. Everything seems like a hack on a hack. There are things like sage/roots that make it a "little" better.
Re: Wordpress on AWS: smooth and pain free
#38I've run a sporadically popular (100s of thousands of uniques on some days) blog on Wordpress for years. All running on a single spot instance (if it was killed I have a script to roll over in minutes).
The database, Wordpress, the file storage. Entirely self contained.
I occasionally persist the AMI so I can spin up a new updated system base, and have regular backups of the files and database. My monthly cost is ~$9 on AWS. I've had literally minutes of downtime over the past several years.
Obviously this guide is geared to a more serious installation, but there is the danger that the more reliable a system becomes, often the less reliable it becomes. EFS and NLB configuration changes or problems taking the system offline, for instance.
Re: Wordpress on AWS: smooth and pain free
#39Why is anyone running WordPress anymore.? So many better options.100s if not 1,000s. The fact that you need elaborate guides to host it one of the most common hosting providers is yet another example. It's junk. Time to move on. Edit: and the down votes are why this piece of garbage lives on. Please stop trying to hide how awful WordPress is. We all know it's terrible. Just because you work on it for a living doesn't…
You don't need an elaborate guide or aws. Plenty of people use it happily on shared hosting or specialized hosting for wp. Or just click to run droplet with everything installed on DO. Plenty of easy ways.
Re: Wordpress on AWS: smooth and pain free
#40Earlier quoted context omitted.
What your requirements? With Google rendering JavaScript any static site generator is probably going to be better. If you need crud functionality any number of hosted and open source crud providers are available. Or just use a hosted site builder. They are all better at this point.
Static site generators are just fine for personal blogs. They don't fit the bill at all when you have a group of people all writing on one blog and you need things like access controls and media file management. Also, not sure why google rendering JavaScript would have any effect on static site generators.
That's why I said it depends on the needs. Read. Stop blindly defending garbage. You can use version control with a static site generator. Otherwise there are hundreds of crud interfaces to edit content with a group that a far superior to WordPress.
JavaScript rendering is if your use case requires dynamically generated content. Again, read. It's based on your needs. Whereas you are defending WordPress because your(not your client's) bank account depends on it. Which I consider very unethical.