Socialengine on Elastic Beanstalk + Github
Has anyone tried this setup? Basically you are freezing the state of your SE install to make it into an application that across multiple servers. You separate out the database (RDS or another EC2 instance) and storage (S3) from the application as it becomes readonly. Updates to the application are done through your git repository, so you would need to do plugin upgrades and so on thorugh that.
I like this idea because of how it scales as well as forcing you to be more mehodical about updates.
Answers: 2 • Score 1 • Views: 1359
by Kapil Jain about
We have setup this enviroment for one of our client. We used an ELB, two EC2 instances, One RDS and Amazon S3. We have fine tuned our EC2 instances for performance tuning so didn't used Elastic Beanstalk. Instead of using git, we used svn and all the latest code have been deployed on ec2 instances within a min or two.This infrastructure seems scalable and able to handle thousands concurrent users on the site.Also we have configured alarm to add/remove ec2 instance whenever its required.
by Eugene about
This sounds pretty interesting! I'll check it out.
Have you already tried it?
There is one issue I see - not all 3rd party plugins support S3.