Skip to content

CNAME file is blown away on every deploy #41

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

Closed
myronmarston opened this issue Jan 29, 2015 · 0 comments
Closed

CNAME file is blown away on every deploy #41

myronmarston opened this issue Jan 29, 2015 · 0 comments

Comments

@myronmarston
Copy link
Member

It took me a while to figure out why our CNAME file wasn't working. We had it in our source branch ut not in our master branch. As github's docs state, it needs to be in the master branch:

https://help.github.com/articles/adding-a-cname-file-to-your-repository/

I added it to master and that made it work. Then I noticed on the next deploy that it was blown away by the deploy (since middleman apparently force pushes -- is that really necessary?).

@JonRowe / @mootpointer -- do either of you know how to configure our deploy so that it won't blow away extra files (such as the CNAME) on each deploy? For now I'm just re-adding it manually after each deploy but that's no fun.

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

No branches or pull requests

1 participant