-
Notifications
You must be signed in to change notification settings - Fork 99
FAQ
Go to you repository settings, scroll down to the GitHub Pages
section:
That's by design, the command 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.
Example:
ng build
echo "my-domain.com" > dist/CNAME
angular-cli-ghpages [OPTIONS]
git clone https://github.com/angular-buch/angular-cli-ghpages.git
cd angular-cli-ghpages
npm link
npm link
is very similar to npm install -g
except that instead of downloading the package
from the NPM repo, the just cloned angular-cli-ghpages/
folder becomes the global package.
Now you can use ngh
via the command line.
Please read the official npm-link documentation
and the npm-link cheatsheet for more information.
"If your site is a User or Organization Page that has a repository named
<username>.github.io
or<orgname>.github.io
, you cannot publish your site's source files from different locations. User and Organization Pages that have this type of repository name are only published from themaster
branch." - GitHub
All this means is that you have to keep your published files in the master
branch.
Create a new branch for your source files, source
for example, and only work from within that branch.
When you're ready to publish your website specify the master
branch by using --branch=master
.