Skip to content

No CNAME for staging. #60

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

Merged
merged 2 commits into from
Feb 2, 2015
Merged

No CNAME for staging. #60

merged 2 commits into from
Feb 2, 2015

Conversation

JonRowe
Copy link
Member

@JonRowe JonRowe commented Feb 1, 2015

Refactor the config to ignore CNAME on staging, fixes #53.

@myronmarston
Copy link
Member

LGTM assuming you've tried staging and prod deploys with this.

@JonRowe
Copy link
Member Author

JonRowe commented Feb 2, 2015

Yep I did, no warning was generated ;)

JonRowe added a commit that referenced this pull request Feb 2, 2015
@JonRowe JonRowe merged commit 4c61e78 into source Feb 2, 2015
@JonRowe JonRowe deleted the staging_no_cname branch February 2, 2015 00:43
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.

Staging deploy results in page build warning email from GitHub
2 participants