And three’s a party.
I’ve been looking for signs of EE deployments on AWS and this is the best I’ve seen. I’m unsure why that might be, but here we are.
I’m migrating EE from a traditional VPS to AWS and will be using as many AWS services as possible to separate configuration and media from the application, so we can update EE and add-ons independently from the actual site, and manage load, backups and dev/test in a more effective way.
If there is interest, perhaps we might share resources.
I’m interested. What can you share? How do you handles dev/test, backup, load balancing and update on AWS?
thanks Filippo
As of yesterday I have a local working Docker setup consisting of a MySQL container, a PHP-FPM container and an NGINX container. I intend to deploy this either via ECS or EB to AWS. I’m intending to use Redis as the Session Store, S3 as the media store, and RDS as the database.
At the moment I am working through dealing with EE and a read-only file-system. The application I’m migrating has stuff scattered all over the place and I’m trying to make sure that I get all the bits, cache, session and media and whatever else I find 😉
To make stuff more interesting, it’s also running an ancient copy of EE, so I’m also doing an upgrade and likely will need to deal with add-on changes as well.
From a Docker perspective, I’m using two minimal Dockerfile set-ups, one for PHP-FPM and one for NGINX. I’m using docker-compose.yml to describe the production environment and docker-compose.override.yml for dev. Both include a relevant environment file that stores passwords, time-zones, etc.
I’m using a Makefile to combine the lot and can now rebuild the environment in seconds. Very helpful when you come across a random MySQL error that only happens in v5.7, but not in v5.6, or when your PHP installation is missing some random module :-|
I have the EE code in a private git repository.
Hope that helps as a start.
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.