AWS, Heroku & DNS

[jenbennings]

• [x] Set up an Idealogue AWS account
• [x] Transfer the Heroku app ownership to Idealogue
• [x] Point brandguide.io at the Heroku app

[haustraliaer]

AWS now setup - details in the Idealogue vault.

Matt can transfer the Heroku app to david@idealogue.io

[mattlenz]

@haustraliaer Done

@jenbennings If you've got a Heroku account, Dave can add you also as a collaborator (heroku sharing:add <email>) -- so you've got permissions to push changes up to the live site in the future.

[haustraliaer]

Yep already done.

[haustraliaer]

All done. Wildcard & root domain now points at heroku, so http://brandguide.io, http://www.brandguide.io and http://whatever-random-sub-domain.brandguide.io -> all point to heroku.

@mattlenz should be able to accept subdomain routes into rails upon creation of a new brandguide, and we should probably setup a generic 404 for handling subdomains that don't exist (rather than getting the heroku "no app found" message.

Specific sub-domains can be set to point at different places also - so admin.brandguide.io could be reserved for our main overview page.

[mattlenz]

@haustraliaer Domains are pointing correctly now (showing Rails 404 if not found). We'll need to create some nicer branded 404/500 error pages (see public/404.html and public/500.html).