>>> is the database synced automatically because both servers will be using the same s3 bucket to pull its data from ?
Currently, ClouSE requires each MySQL server to work with unique cloud storage location. Locations could be in the same bucket, but in that case they must have different prefixes, e.g. one server would work with s3.amazonaws.com/mybucket/db0 and another server would work with s3.amazonaws.com/mybucket/db1
>>> if not how do i set this up to run on multiple load balanced apache/mysql servers?
You can start with the ready-to-run WordPress-on-S3 AMI and split it into frontend(s) and a backend. On the backend you’d keep MySQL+ClouSE and on the frontend(s) you’d keep WordPress+WP2Cloud. WP2Cloud makes the frontend stateless (that’s yet another advantage of storing media in S3 — in addition to leveraging S3’s high durability and scalability), so you can run as many frontends as you need to accommodate the load.
I think you can even use Amazon Beanstalk to do the heavy lifting of provisioning, scaling and balancing of WP2Cloud-enabled WordPress frontends.
>>> can i run it on amazon rds mysql and connect to it from multiple app servers?
AFAIK, RDS folks won’t let you run a custom engine on their MySQL servers. That said, feel free to ask them. On our side, we’d be happy to offer ClouSE as part of RDS’ MySQL stack.
Thread Starter
ds123
(@ds123)
thanks for the reply ..i’m still a little unclear though my question is will all the ec2 servers running mysql / clouSE on them have the same data coming from mysql?
i don’t see how its possible unless all the ec2 instances use the same bucket to pull data from ?
see what i mean? say i have ec2_server_1 and ec2_server_2 …both running your plugin to handle offloading images to s3
say one of my users uploads an image via wordpress and they are on ec2_server_1 …..will the users on ec2_server_2 see the image right away?
i’m planning to use your plugin only for offloading images to s3 not to handle the actual wordpress mysql that i’m using another solution for
If I understand you correctly, you want to have multiple WordPress web tiers (a.k.a. application tiers, a.k.a. frontends) to serve pages for one website. The way you can do it with WP2Cloud is to have a single data tier (a.k.a. backend) to run MySQL+ClouSE, and configure the web tiers to use that data tier as the database (the data tier would really store all data in S3 and would be effectively just MySQL API for S3).
Currently, WP2Cloud expects that the cloud media table resides in the same database as the core WordPress data. We could implement a feature, which would allow you to configure WP2Cloud such that it would keep the cloud media on a separate MySQL server, so that you can store core WordPress data in one MySQL server, and media on another MySQL+ClouSE server. If you think this feature would work for you, please contact us.
How to use WP2Cloud when you cannot modify MySQL installation?
A number of users, who would like to use cloud storage for storing and serving media files, reached out to us with this question. Typically users run into this limitation due to the lack of permissions in shared hosting environments or when they have to deal with older versions of MySQL.
We decided to go ahead and unblock these users by enabling support for Media Server-based configuration. WP2Cloud plugin now can be configured to use a separate database server to handle upload files.
For more details please follow Advanced deployment configuration with Media Server section of WP2Cloud install instructions.
