0

These steps used to work. First create the repository:

https://github.com/fireflysemantics/help-service-parts

Add the remote for it

git remote add origin [email protected]:fireflysemantics/help-service-parts.git

Add angular-cli-ghpages:

ng add angular-cli-ghpages

And deploy:

ng deploy --base-href=https://help-service-parts.fireflysemantics.com/ --cname=help-service-parts.fireflysemantics.com

After doing this it does create the cname record and I see all the files in the gp-pages branch:

https://github.com/fireflysemantics/help-service-parts

However when looking at the settings the custom domain field is not populated with the cname domain, and it says the site is ready to be published:

Your site is ready to be published at http://fireflysemantics.github.io/help-service-parts/.

But it does not appear at the url:

http://fireflysemantics.github.io/help-service-parts/

I have DNS set to resolve it on:

https://help-service-parts.fireflysemantics.com 

Also.

Thoughts?

3
  • Did you try removing the slash from the url? ng deploy --base-href='https://help-service-parts.fireflysemantics.com' Commented Jan 4, 2020 at 6:16
  • I think that was it - Thank you!!! Commented Jan 4, 2020 at 6:40
  • Posted as the answer. xD Commented Jan 4, 2020 at 6:42

1 Answer 1

2

I'm the author of angular-cli-ghpages. The combined usage of the parameters --cname and --base-href is not expected.

This should work if you do not want to use your own domain:

ng deploy --base-href=/help-service-parts/

And this is what you set when you have your own domain:

ng deploy --cname=help-service-parts.fireflysemantics.com
Sign up to request clarification or add additional context in comments.

Comments

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.