Open ripper234 opened 8 years ago
Cross that, the current system is deployed to a test AWS, but it should still be deployed to production.
No database for now, using an internal MondoDB
No database for now, using an internal MondoDB
Meaning - we scratched anything to do with database from this issue (but see #21). This issue (#10) is just about an app server & DNS config.
@omerpines can we please move DNS management to AWS / Route 53? There will constantly be records to be updated/change. I understand a lot may get broken, yet DNS-wise it's actually very easy to confirm/test all changes...
Right After Midburn 2016 On Apr 5, 2016 9:55 PM, "Elad Gariany" notifications@github.com wrote:
@omerpines https://github.com/omerpines can we please move DNS management to AWS / Route 53? There will constantly be records to be updated/change. I understand a lot may get broken, yet DNS-wise it's actually very easy to confirm/test all changes...
— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub https://github.com/Midburn/playainfo/issues/10#issuecomment-205948391
We have a production server (micro for now):
Instance: i-89a9f851Public DNS:
ec2-54-187-29-57.us-west-2.compute.amazonaws.com
@amotenko I'm sending you the access credentails.
We are late on schedule, I'm pushing this to a later milestone.
We want to deploy the system on a server that is managed by Midburn's AWS, not @amotenko 's.