Merge pull request #127 from kuc2477/patch-1
Add an warning for using the CNAME parameter
This commit is contained in:
commit
1d9e5b1b66
|
@ -44,15 +44,18 @@ with behavior for GitHub Pages.
|
||||||
|
|
||||||
## CNAME Support
|
## CNAME Support
|
||||||
|
|
||||||
If you want to use a [CNAME :ext](https://en.wikipedia.org/wiki/CNAME) with
|
If you want to use a custom domain with GitHub pages (also known as a
|
||||||
GitHub pages and Lektor you can provide the intended CNAME with the `?cname`
|
[CNAME :ext](https://en.wikipedia.org/wiki/CNAME)), provide the intended
|
||||||
parameter:
|
CNAME in the target URL using the `?cname` parameter:
|
||||||
|
|
||||||
```ini
|
```ini
|
||||||
[servers.production]
|
[servers.production]
|
||||||
target = ghpages://your-user/your-repository?cname=www.example.com
|
target = ghpages://your-user/your-repository?cname=www.example.com
|
||||||
```
|
```
|
||||||
|
|
||||||
|
Note that this will overwrite whatever custom domain you may have set on
|
||||||
|
GitHub with every deployment.
|
||||||
|
|
||||||
For more information about how CNAMEs work with GitHub you can read about
|
For more information about how CNAMEs work with GitHub you can read about
|
||||||
the feature in the GitHub help center:
|
the feature in the GitHub help center:
|
||||||
[Adding a CNAME file to your repository
|
[Adding a CNAME file to your repository
|
||||||
|
|
Loading…
Reference in New Issue