Closed lcreid closed 5 years ago
It might just be easiest to admit that we need to pay for another server when we want test/staging/training.
Or use Capistrano. We've had to use Capistrano for some clients, and now that we have it figured out, there's no real reason not to use it for AWS deploys as well.
Capistrano is the right answer to this.
There is an immediate need to deploy to staging, which would be an Internet-accessible site that is as identical as possible to production (except for data in the database). "Identical" includes the way it's deployed. The purpose in the short term at least is to be able to test and fix deploys without affecting production.
Because of the way we share environments on our production server, it's not obvious how CodeDeploy can be made to deploy to different directories, without a lot of risky manual intervention.