Closed maxx1128 closed 6 years ago
SSL included from the start? Is it free?
Yep :)
ok. If we're pre-compiling as a static site does it matter what frameworks are supported? Having a dev url is nice.
It's any framework really. You just set a branch, a build command, and it uses that output as the site. I'm currently using it with Gatsby, a static-site generator on react, and it compiles fine. They have docs for all frameworks they explicitly support, like Jekyll, but even if it doesn't list it then it should work fine.
FWIW the DNS migration, which is necessary to move to Netify, is non trivial.
@treznick what do you mean?
@maxx1128 we're just now deploying Continuous Deployment (including build) via travis-ci so the hosting provider supporting our framework/build doesn't matter. This gives us ultimate flexibility on frameworks and build pipeline.
@jnimety I meant that moving where the records are listed requires some measure of coordination, but I may be mistaken on that
I don't think we would move DNS, just change an A record or two, right?
@jnimety you'd know better than I would.
On Fri, Apr 27, 2018 at 2:42 PM Joel Nimety notifications@github.com wrote:
I don't think we would move DNS, just change an A record or two, right?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/newhavenio/newhavenio.github.io/issues/65#issuecomment-385059155, or mute the thread https://github.com/notifications/unsubscribe-auth/AAlwA74fe4nJO3GMcwiDGdYbB2L66k7Wks5ts2aAgaJpZM4TlPfS .
https://blog.github.com/2018-05-01-github-pages-custom-domains-https/
Given that GH Pages now supports this, I'm going to close this issue. Thanks for looking into this @jnimety and @maxx1128
1) Included from the start, more convenient 2) No intermediary that would have an insecure connection 3) Flexibility to use any framework, not just Jekyll 4) Can deploy a working version to a hidden URL so it's easier to test and provide feedback before official launch 5) Can still host source code in Github repo for collaboration 6) If the build fails it'll fall back to the last successful build version, avoiding showing users a broken experience