Fog Creek

How To: Configure a Custom Domain for HyperDev Projects

For now, every project on HyperDev has an auto-generated sub-domain name that you can view from our hyperdev.space domain. We realize that you’d like to not only be able to set your own project names, but also use your own domain names. We plan to add those features, but for now, we have a workaround that we hope will suffice for some of you. It’s a little fiddly, but we’re going to share some example settings that you can use in CloudFront and Route 53 to serve a HyperDev project from a custom domain name. In our example settings we’re serving the HyperDev project, flicker-swoop, from the custom domain, lsystems.danielx.net.

What You’ll Need

  • Your HyperDev project URL
  • Your own custom domain
  • A free AWS account

How It Works

Replace your own HyperDev project URL and custom domain name wherever you see ‘flicker-swoop.hyperdev.space’ and ‘lsystems.danielx.net’ respectively, in the details provided below, on your own CloudFront and Route 53 settings screens. Note that you can click on the settings image to see a larger version.

Phase 1: Origin Settings in CloudFront

7b07db7412583b9c6cdb18c4762caa1ba96eb170_1_690x395

Phase 2: Default Cache Behavior Settings in CloudFront

7e285e682275101e13bb340ef3ee3f7a5659d3cd_1_381x500

Phase 3: Distribution Settings in CloudFront

81844bf216e942731202b264c334cb00d02252d5_1_690x397

Phase 4: Add the Route 53 Record Set

4efc93c53514bde2bb29d07540db854047900d32

Wrap Up

And that should be it. It’s possible to adjust some of the settings to your preference, but that’s a working setup. We do plan to add CNAME support and the ability to set your own project names soon. But in the meantime, this is an option that you can use today to be able to use your own custom domain name with HyperDev.

You can see example projects on our Community Projects page. And if you get stuck, let us know on the forum and we can help you out.