Support https://adhearsion.com/

[sfgeorge]

I think we need to cover the following bases:

1. Get https://adhearsion.com/ to work
2. Redirect all http traffic to https

Having a site on http:// has a negative impact on security and visitor confidence:

Additionally, it has a negative impact on SEO for those who are searching for a great platform for controlling communications.

There are a few good, free options for free SSL these days, including Let's Encrypt and CloudFlare's Universal SSL.

[chewi]

The ageing gems are also a concern. However, most of the dynamic elements seem redundant now. Would it make more sense to turn it into a static site? Probably cheaper too.

[sfgeorge]

Good point, that would reduce surface area of risk.

[benlangfeld]

If you used middleman, you could render the existing templates at compile-time, and just host from S3 or similar.

[chewi]

@benlangfeld, exactly what I was thinking as I've used Middleman before. Would GitHub Pages even be an option?

[benlangfeld]

Yes, looks like it. If someone can get middleman working, just let me know if there’s anything you need me to do with configuration/DNS/etc

[sfgeorge]

Awesome. If we end up doing middleman -> github pages, I think I found the necessary deets for SSL of custom github-io domains here:

GitHub Blog: Custom domains on GitHub Pages gain support for HTTPS

Basically may just require a CNAME 💪

[sfgeorge]

Sorry, please ignore my CNAME suggestion. @adhearsion.com has active MX records, and using a CNAME will break mail functionality for the domain. as suggested here on S.O., a good approach is to use A, ALIAS or ANAME - but not a CNAME.

GitHub Help: Setting up an apex domain