You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
github pages deploy create wrong base href for repos with camelcase names #3146
This also creates a problem for github pages that use custom domains.
In which case the base href needs to default back to just "/" and no longer the name of the repo, or "/some-repo".
Because unlike the github page, which serves content from: some-account.github.io/some-repo
A custom domain no longer has the extra file path ie, not this: myWebsite.com/some-repo
Instead it servers from myWebsite.com, and so it needs a "/" base href.
Right now the solution is: ng github-pages:deploy --base-href /
Activity
rolyatsats commentedon Dec 1, 2016
The
ng github-pages:deploycommand derivesbaseHreffrompackageName, which is pulled frompackage.json.package.jsonis created throughember-cli/lib/models/blueprint.jswhich uses thenormalizeEntityNamefunction todasherizeas they call it.There must be a way to override the
normalizeEntityNamefunction to support camelCase.WebDesignerKits commentedon Dec 28, 2016
This also creates a problem for github pages that use custom domains.
In which case the base href needs to default back to just "/" and no longer the name of the repo, or "/some-repo".
Because unlike the github page, which serves content from: some-account.github.io/some-repo
A custom domain no longer has the extra file path ie, not this: myWebsite.com/some-repo
Instead it servers from myWebsite.com, and so it needs a "/" base href.
Right now the solution is: ng github-pages:deploy --base-href /
filipesilva commentedon Feb 3, 2017
Closed via #4385.
angular-automatic-lock-bot commentedon Sep 6, 2019
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.