[feature request] CNAME file for custom domains is replaced

[PascalTemel]

If your github pages project is deployed on a custom domain, ngh overwrites this file and it has to be recreated after every push.

[JohannesHoppe]

That's by design, it overrides everything.
If it wouldn't do that, all the hashed bundles would stay, too!

You have to put a CNAME file into your dist folder.
I should start a wiki! :-)

[PascalTemel]

It might be intended, but it really seems like bad design. I didnt expect to have to do that since ng gh-pages didnt delete that file either. Maybe its worth discussing this again internally, or rethinking it.

[JohannesHoppe]

Yeah, we have to see. I will keep that issue open for a while, to see other peoples opinion on that issue.
The original angular-cli command got too complicated and now it's gone. 😄 My goal is to keep it simple.

What do you think about a --cname=my.domain.org command line option?
Meanwhile, I created a FAQ:
https://github.com/angular-buch/angular-cli-ghpages/wiki/FAQ

[PascalTemel]

A command line option would be enough for me.

[JohannesHoppe]

That's easy.
The quick way: You send a PR! ;-)
The slower way: I will do that if there is some time!

[PascalTemel]

I don't think I have the necessary know-how to do it, but I might look into it sometime.

[coryshaw1]

I ended up making an extra build step in my Travis CI config. I added a copy:cname script in my package.json, and just called it after ng build step.

"copy:cname": "cp ./CNAME ./dist/CNAME"

This works fine, but a command line option would be nice!

[JohannesHoppe]

I will add this command (--cname=my.domain.org) in v.0.5.1 together with an option to create the 404.html .

[alexjlockwood]

Hi there, just wondering did this make it into v0.5.1?