I am a grown up Graffiti kid from West Berlin.
Nothing here yet.
No blogs yet.
@alistek I do not have much first hand experience with WordPress. From our point of view WP does not play very well with the modern development patterns we like so much – Composer, Git … Our advice to use WP on fortrabbit together with Bedrock, which is a bit of hack. Keeping everything together on one host is a good idea! When you dare to go into DevOps a bit further you might consider to put everything on AWS, leveraging multiple services. This post illustrates and explains a basic setup using: ELB, EC2, S3, RDS. It's basically how the managed fortrabbit infrastructure looks as well. Bottom line: Sorry no practical advice here. But maybe be careful about shared network solutions to share data across multiple hosts and go the other way around and offshore files in the first place. Have a look at flysystem and WP Offload S3 Lite . BTW: AWS is building a shared network solution ( EFS ) for their services as well, but it already takes much longer than first anticipated — it's complicated.
I can totally understand that a shared network storage is the first option to think of, but maybe an offsite object storage is a better solution? Think of an 12-factor App with ephemeral storage where you separate code from content + abstract the file system. How to implement: take your WordPress (Drupal …) and plug in an AWS S3 add-on. This transfers all files to a cloud storage ans serves them from there. Disclaimer: I am fortrabbit co-founder. We are specialized in scalable PHP hosting and we used to have an attached network storage for our Old Apps are now replacing with an Object Storage instead.