Closed subhankarb closed 7 years ago
@subhankarb write out step by step what we do to setup the SSL stuff:
Original hackmd pad
@rufuspollock
Facing issue with naked domain. I created subdomain www
which will point to cloudfront
. But was not finding any way to route http://datapackaged.com
to www.datapackaged.com
.
If i was trying to redirect http://datapackaged.com
to www.datapackaged.com
, one record with subdomain was creating with record type A
. Then i was not able to add another record for the subdomain www
with type CNAME
.
I found some way to resolve this. Steps to fix this
Remove WWW:
option@subhankarb can you describe naked domain issue more precisely.
I also emphasize that we don't want to redirect datapackaged.com to www.datapackaged.com -- we just want to use datapackaged.com.
The way we could point domain to cloudfront is like:
Go to dreamhost
manage DNS. Go to
datapackaged.com
]But the problem is for naked domain datapackaged.com
we can not set CNAME
.
So how can we point datapackaged.com
to cloudfront
.
AWS route53
has option alias
to point domain to any distribution. But in dreamhost i am not able to find any option.
@subhankarb can you clarify in your steps by step where things happen. e.g. "Add a custom DNS record ..." -- where do you do this.
FIXED website is up https://datapackaged.com
We have to setup the site in production environment - http://datapackaged.com/
Tasks
Run automated deploy scriptSet up infrastructure (AWS stuff, Auth0) (automated)Logging (by zappa)Generate certificatesCertificate for S3 cloudfrontCertificate for API Gateway custom domainAs we switched now to use heroku none of steps above are necessary