ドキュメントには頻繁に更新が加えられ、その都度公開されています。本ページの翻訳はまだ未完成な部分があることをご了承ください。最新の情報については、英語のドキュメンテーションをご参照ください。本ページの翻訳に問題がある場合はこちらまでご連絡ください。
記事のバージョン: Enterprise Server 2.16

About GitHub Pages

You can use GitHub Pages to host a website about yourself, your organization, or your project directly from a GitHub Enterprise repository.

GitHub Pages は、GitHub Free のパブリックリポジトリ、GitHub Pro のパブリックおよびプライベートリポジトリ、GitHub Team、GitHub Enterprise Cloud、GitHub Enterprise Server で利用いただけます。

In this article

](#about-github-pages)

GitHub Pages ](#guidelines-for-using-github-pages)

GitHub Pages ](#mime-types-on-github-pages)

About GitHub Pages

GitHub Pages is a static site hosting service that takes HTML, CSS, and JavaScript files straight from a repository on GitHub Enterprise, optionally runs the files through a build process, and publishes a website. You can see examples of GitHub Pages sites in the GitHub Pages examples collection.

To get started, see "Creating a GitHub Pages site."

Types of GitHub Pages sites

There are three types of GitHub Pages sites: project, user, and organization. Project sites are connected to a specific project hosted on GitHub Enterprise, such as a JavaScript library or a recipe collection. User and organization sites are connected to a specific GitHub Enterprise account.

The source files for a project site are stored in the same repository as their project.

The URL where your site is available depends on whether subdomain isolation is enabled for your 使用している GitHub Enterprise Serverインスタンス.

Type of site Subdomain isolation enabled Subdomain isolation disabled
User

http(s)://pages.[hostname]/<username>/<repository>/ | http(s)://[hostname]/pages/<username>/<repository>/ | Organization | http(s)://pages.[hostname]/<organization>/<repository>/ | http(s)://[hostname]/pages/<organization>/<repository>/ | Project site owned by user account | http(s)://pages.[hostname]/<username>/<repository>/ | http(s)://[hostname]/pages/<username>/<repository>/ Project site owned by organization account | http(s)://pages.[hostname]/<orgname>/<repository>/ | http(s)://[hostname]/pages/<orgname>/<repository>/

For more information, see "Enabling subdomain isolation" or contact your site administrator.

Note: Repositories using the legacy <user>.github.com naming scheme will still be published, but visitors will be redirected from http(s)://<username>.github.com to http(s)://<username>.github.io. If both a <user>.github.com and <user>.github.io repository exist, only the <user>.github.io repository will be published.

Publishing sources for GitHub Pages sites

The publishing source for your GitHub Pages site is the branch or folder where the source files for your site are stored. All sites have a default publishing source, and project sites have additional publishing sources available.

The default publishing source for user and organization sites is the master branch. If the repository for your user or organization site has a master branch, your site will publish automatically from that branch. You cannot choose a different publishing source for user or organization sites.

The default publishing source for a project site is the gh-pages branch. If the repository for your project site has a gh-pages branch, your site will publish automatically from that branch.

Project sites can also be published from the master branch or a /docs folder on the master branch. To publish your site from one of these sources, you must configure a different publishing source. For more information, see "Configuring a publishing source for your GitHub Pages site."

If you choose the /docs folder of the master branch as your publishing source, GitHub Pages will read everything to publish your site, including the CNAME file, from the /docs folder. For example, when you edit your custom domain through the GitHub Pages settings, the custom domain will write to /docs/CNAME.

Static site generators

GitHub Pages publishes any static files that you push to your repository. You can create your own static files or use a static site generator to build your site for you. You can also customize your own build process locally or on another server. We recommend Jekyll, a static site generator with built-in support for GitHub Pages and a simplified build process. For more information, see "About GitHub Pages and Jekyll."

If you want to use a static site generator other than Jekyll, disable the Jekyll build process by creating an empty file called .nojekyll in the root of your publishing source, then follow your static site generator's instructions to build your site locally.

GitHub Pages does not support server-side languages such as PHP, Ruby, or Python.

Usage limits

GitHub Pages sites are subject to the following usage limits:

MIME types on GitHub Pages

A MIME type is a header that a server sends to a browser, providing information about the nature and format of the files the browser requested. GitHub Pages supports more than 750 MIME types across thousands of file extensions. The list of supported MIME types is generated from the mime-db project.

While you can't specify custom MIME types on a per-file or per-repository basis, you can add or modify MIME types for use on GitHub Pages. For more information, see the mime-db contributing guidelines.

Further reading

担当者にお尋ねください

探しているものが見つからなかったでしょうか?

弊社にお問い合わせください