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.

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

Set the server’s fqdn to be tessel.io #27

Merged
merged 1 commit into from Nov 24, 2015
Merged

Set the server’s fqdn to be tessel.io #27

merged 1 commit into from Nov 24, 2015

Conversation

reconbot
Copy link
Member

This should tell nginx to use tessel.io but keep mgmt functions active at tessel-io.bocoup.com

@tkellen did I miss anything?

@tkellen
Copy link

tkellen commented Nov 24, 2015

Hmm. Why do you need a mgmt_fqdn? The place that configures what Ansible communicates with is the inventory file. Also, from a SEO perspective there should only be one canonical domain. If you remove the mgmt_fqdn tessel-io.bocoup.com will redirect correctly to tessel.io.

@tkellen
Copy link

tkellen commented Nov 24, 2015

PS: this is what configures which server you'll be deploying to:
https://github.com/tessel/tessel.io/blob/master/deploy/ansible/inventory/production#L4

You could even have that be tessel.io too, and do this to override:
tessel.io ansible_ssh_host=tessel-io.bocoup.com

@reconbot
Copy link
Member Author

My reasoning is that once the ssl terminators are in place the fqdn of the machine and the fqdn of the website will point to different things. Same goes for if we used a CDN or any of that jazz.

You got me with the one canonical domain.

@reconbot
Copy link
Member Author

I'm declaring YAGNI on keeping fqdn and hostnames separate until we actually need it.

reconbot added a commit that referenced this pull request Nov 24, 2015
Set the server’s fqdn to be tessel.io
@reconbot reconbot merged commit c3c3cfa into master Nov 24, 2015
@reconbot reconbot deleted the fqdn branch November 24, 2015 15:17
@tkellen
Copy link

tkellen commented Nov 24, 2015

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants