Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Change to .com #210

Closed
ghost opened this issue Mar 15, 2017 · 4 comments
Closed

Change to .com #210

ghost opened this issue Mar 15, 2017 · 4 comments
Labels
enhancement New feature or enhancement of existing functionality priority-2 Second highest priority, should be worked on as soon as the Priority-1 issues are finished

Comments

@ghost
Copy link

ghost commented Mar 15, 2017

Alter .com and .io DNS and Heroku settings
Main site = .com
.io site = forwards to .com
@ghost ghost added the priority-2 Second highest priority, should be worked on as soon as the Priority-1 issues are finished label Mar 15, 2017
@ghost ghost self-assigned this Mar 15, 2017
@nelsonic nelsonic added the enhancement New feature or enhancement of existing functionality label Mar 15, 2017
@ghost
Copy link
Author

ghost commented May 11, 2017

www.dwyl.com is now working
Next stage is to get the dwyl.com root domain to work without forwarding to www

iwantmyname said:

You would need to check out one of the hosting providers that allow this feature:

  • CloudFlare
  • DNSMadeEasy
  • DNSimple
  • PointDNS
  • Amazon Route 53 (only for hosting on AWS)

Heroku instructions are also here:
https://devcenter.heroku.com/articles/custom-domains#add-a-custom-root-domain

@nelsonic do you have any thoughts or objections to us moving the hosting to Amazon Route 53/AWS?

@ghost ghost assigned nelsonic and unassigned ghost May 11, 2017
@iteles
Copy link
Member

iteles commented May 11, 2017

@markwilliamfirth Only that we lose all the nice devops layer functionality of heroku.

What is the negative effect of having the www routing to the non-www? Does it cause any issues for SEO for example?

@iteles iteles assigned ghost and unassigned nelsonic May 11, 2017
@nelsonic
Copy link
Member

We aren't using AWS for the dwyl website. It's more expensive and slower than alternative IaaS providers.
If we moved to AWS today we would spend more money on infrastructure, add complexity and have zero added value.
When we move from Heroku we will do it right.

@ghost
Copy link
Author

ghost commented Jun 15, 2017

Based on comments above, sticking with www subdomain for now

@ghost ghost closed this as completed Jun 15, 2017
@Cleop Cleop mentioned this issue Jun 19, 2017
Closed
@ghost ghost mentioned this issue Sep 7, 2017
Closed
@jammur jammur unassigned ghost Dec 14, 2017
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or enhancement of existing functionality priority-2 Second highest priority, should be worked on as soon as the Priority-1 issues are finished
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@nelsonic @iteles