| Sep | OCT | Nov |
| 08 | ||
| 2019 | 2020 | 2021 |
COLLECTED BY
Collection: github.com
gem update bundler in your terminal before following the next steps.
(一)Add the following to your project's Gemfile:
gem 'github-pages', group: :jekyll_plugins(一)Run
bundle install
Note: You are not required to install Jekyll separately. Once the github-pages gem is installed, you can build your site using jekyll build, or preview your site using jekyll serve. For more information about installing Jekyll locally, please see the GitHub Help docs on the matter.
make image from the root of the pages-gem directory to build an image which will be tagged as gh-pages
●Alternatively use make image_alpine for a smaller alpine-based image
(一)Start an instance of the server by running either:
●SITE=PATH_TO_YOUR_PROJECT make server from the root of the gh-pages repository (where the Makefile resides) or
●SITE=PATH_TO_YOUR_PROJECT docker run --rm -p 4000:4000 -v `realpath ${SITE}`:/src/site gh-pages from any directory or
●github-pages $PATH_TO_YOUR_PROJECT from any directory when func.sh has been sourced into your terminal session or
●github-pages from the directory of the Jekyll site to be previewed when func.sh has been sourced into your terminal session.
Note: the github-pages function may be enabled by sourcing func.sh. This can be done by appending
source $PATH_TO_THIS_DIRECTORY/contrib/func.shto the scripts that load on initiation of a terminal session (usually
~/.bashrc on bash or ~/.zshrc on zsh).:
Running of github-pages inside a directory of a Jekyll site spawns a server on port 4000. One may explicitly provide a path to a Jekyll site and a port by running github-pages $PATH $PORT. This approach is provided as a user-friendlier alternative to the make serverordocker run invocations mentioned as the first options in step 2.
The ordering of the arguments for the github-pages function is based on the assumption that it is more likely to need to specify a custom path rather than a custom port.
github-pages command.
$ bundle exec github-pages versions +---------------------------+---------+ | Gem | Version | +---------------------------+---------+ | jekyll | x.x.x | | kramdown | x.x.x | | liquid | x.x.x | | .... | .... | +---------------------------+---------+Note, you can also pass the
--gemfile flag to get the dependencies listed in a valid Gemfile dependency format. You can also see a list of the live dependency versions at pages.github.com/versions.
$ github-pages health-check Checking domain foo.invalid... Uh oh. Looks like something's fishy: A record points to deprecated IP addressSee the GitHub Pages Health Check documentation for more information.
jekyll buildorjekyll serve command with DISABLE_WHITELIST=true. This will allow your site to use any plugin listed in your site's gems configuration flag. Please note, however, this option is only available when previewing your Jekyll site locally.
gem update github-pages, or if you've installed via Bundler, bundle update github-pages.
mailto links prior to 1.9.3. In order to ensure that building locally consistently results in the same build as what appears when published, it's essential that Ruby itself is versioned along side the Gem, despite no known incompatibilities.
script/release from the master branch.