web/_posts/2019-08-09-getting-started.md

171 lines
7.8 KiB
Markdown
Raw Normal View History

2019-09-30 15:38:58 +03:00
---
2019-11-18 17:36:22 +03:00
title: Getting Started
2022-03-16 21:05:45 +03:00
author: cotes
2019-09-30 15:38:58 +03:00
date: 2019-08-09 20:55:00 +0800
categories: [Blogging, Tutorial]
2019-11-05 17:14:02 +03:00
tags: [getting started]
2020-06-06 07:45:33 +03:00
pin: true
2019-09-30 15:38:58 +03:00
---
2021-01-25 15:19:50 +03:00
## Prerequisites
Follow the instructions in the [Jekyll Docs](https://jekyllrb.com/docs/installation/) to complete the installation of `Ruby`, `RubyGems`, `Jekyll`, and `Bundler`. In addition, [Git](https://git-scm.com/) is also required to be installed.
2019-09-30 15:38:58 +03:00
2020-08-02 21:25:40 +03:00
## Installation
2019-09-30 15:38:58 +03:00
2021-09-29 15:44:00 +03:00
### Creating a New Site
2020-08-02 21:25:40 +03:00
2021-09-29 15:44:00 +03:00
There are two ways to create a new repository for this theme:
2021-01-25 15:19:50 +03:00
- [**Using the Chirpy Starter**](#option-1-using-the-chirpy-starter) - Easy to upgrade, isolates irrelevant project files so you can focus on writing.
- [**Forking on GitHub**](#option-2-forking-on-github) - Convenient for custom development, but difficult to upgrade. Unless you are familiar with Jekyll and are determined to tweak or contribute to this project, this approach is not recommended.
2020-08-02 21:25:40 +03:00
2021-09-29 15:44:00 +03:00
#### Option 1. Using the Chirpy Starter
2020-08-02 21:25:40 +03:00
2021-09-29 15:44:00 +03:00
Create a new repository from the [**Chirpy Starter**][use-starter] and name it `<GH_USERNAME>.github.io`, where `GH_USERNAME` represents your GitHub username.
2020-08-02 21:25:40 +03:00
2021-09-29 15:44:00 +03:00
#### Option 2. Forking on GitHub
[Fork **Chirpy**](https://github.com/cotes2020/jekyll-theme-chirpy/fork) on GitHub and rename it to `<GH_USERNAME>.github.io`. Please note that the default branch code is in development. If you want the site to be stable, please switch to the [latest tag][latest-tag] and start writing.
2020-08-02 21:25:40 +03:00
2021-01-25 15:19:50 +03:00
And then execute:
2020-08-02 21:25:40 +03:00
2021-01-25 15:19:50 +03:00
```console
2021-09-29 15:44:00 +03:00
$ bash tools/init.sh
2021-01-25 15:19:50 +03:00
```
2022-01-21 16:38:50 +03:00
> If you don't want to deploy your site on GitHub Pages, append option `--no-gh` at the end of the above command.
2022-02-12 21:10:52 +03:00
{: .prompt-info }
2021-09-29 15:44:00 +03:00
The above command will:
2021-07-19 17:24:04 +03:00
2021-09-29 15:44:00 +03:00
1. Removes some files or directories from your repository:
2022-01-22 18:21:00 +03:00
- `.travis.yml`{: .filepath}
- files under `_posts`{: .filepath}
2021-07-19 17:24:04 +03:00
2022-01-22 18:21:00 +03:00
2. If the option `--no-gh` is provided, the directory `.github`{: .filepath} will be deleted. Otherwise, set up the GitHub Action workflow by removing the extension `.hook`{: .filepath} of `.github/workflows/pages-deploy.yml.hook`{: .filepath}, and then remove the other files and directories in the folder `.github`{: .filepath}.
2022-01-22 18:21:00 +03:00
3. Removes item `Gemfile.lock` from `.gitignore`{: .filepath}.
2021-01-25 15:19:50 +03:00
2021-09-29 15:44:00 +03:00
4. Creates a new commit to save the changes automatically.
2021-01-25 15:19:50 +03:00
2021-09-29 15:44:00 +03:00
### Installing Dependencies
2020-04-12 19:38:56 +03:00
Before running for the first time, go to the root directory of your site, and install dependencies as follows:
2021-01-25 15:19:50 +03:00
```console
$ bundle
```
2020-04-12 19:38:56 +03:00
2021-01-25 15:19:50 +03:00
## Usage
2019-09-30 15:38:58 +03:00
2020-08-02 21:25:40 +03:00
### Configuration
2019-09-30 15:38:58 +03:00
2022-01-22 18:21:00 +03:00
Update the variables of `_config.yml`{: .filepath} as needed. Some of them are typical options:
- `url`
- `avatar`
- `timezone`
2021-02-01 23:23:53 +03:00
- `lang`
2020-03-04 15:07:02 +03:00
### Customizing Stylesheet
2021-07-19 17:24:04 +03:00
2022-01-22 18:21:00 +03:00
If you need to customize the stylesheet, copy the theme's `assets/css/style.scss`{: .filepath} to the same path on your Jekyll site, and then add the custom style at the end of the style file.
2021-07-19 17:24:04 +03:00
2022-01-22 18:21:00 +03:00
Starting from [`v4.1.0`][chirpy-4.1.0], if you want to overwrite the SASS variables defined in `_sass/addon/variables.scss`{: .filepath}, create a new file `_sass/variables-hook.scss`{: .filepath} and assign new values to the target variable in it.
2021-07-19 17:24:04 +03:00
2022-02-09 22:16:00 +03:00
### Customing Static Assets
2022-02-14 14:55:44 +03:00
Static assets configuration was introduced in version `5.1.0`. The CDN of the static assets is defined by file `_data/assets/cross_origin.yml`{: .filepath }, and you can replace some of them according to the network conditions in the region where your website is published.
2022-02-09 22:16:00 +03:00
2022-02-14 14:55:44 +03:00
Also, if you'd like to self-host the static assets, please refer to the [_chirpy-static-assets_](https://github.com/cotes2020/chirpy-static-assets#readme).
2022-02-09 22:16:00 +03:00
2021-01-25 15:19:50 +03:00
### Running Local Server
2019-09-30 15:38:58 +03:00
2020-08-02 21:25:40 +03:00
You may want to preview the site contents before publishing, so just run it by:
2019-09-30 15:38:58 +03:00
2021-01-25 15:19:50 +03:00
```console
2020-11-19 16:32:50 +03:00
$ bundle exec jekyll s
2019-09-30 15:38:58 +03:00
```
2021-01-25 15:19:50 +03:00
Or run the site on Docker with the following command:
2021-09-29 15:44:00 +03:00
```console
2021-01-25 15:19:50 +03:00
$ docker run -it --rm \
--volume="$PWD:/srv/jekyll" \
-p 4000:4000 jekyll/jekyll \
2020-11-19 16:32:50 +03:00
jekyll serve
```
2021-09-29 15:44:00 +03:00
After a while, the local service will be published at _<http://127.0.0.1:4000>_.
2022-01-11 13:33:05 +03:00
## Deployment
2020-08-02 21:25:40 +03:00
2022-01-22 18:21:00 +03:00
Before the deployment begins, check out the file `_config.yml`{: .filepath} and make sure the `url` is configured correctly. Furthermore, if you prefer the [**project site**](https://help.github.com/en/github/working-with-github-pages/about-github-pages#types-of-github-pages-sites) and don't use a custom domain, or you want to visit your website with a base URL on a web server other than **GitHub Pages**, remember to change the `baseurl` to your project name that starts with a slash, e.g, `/project-name`.
2020-08-02 21:25:40 +03:00
2021-01-26 21:56:38 +03:00
Now you can choose ONE of the following methods to deploy your Jekyll site.
2019-09-30 15:38:58 +03:00
2022-09-10 12:23:20 +03:00
### Deploy by Using GitHub Actions
2020-01-04 12:05:41 +03:00
2022-09-10 12:23:20 +03:00
Ensure your Jekyll site has the file `.github/workflows/pages-deploy.yml`{: .filepath}. Otherwise, create a new one and fill in the contents of the [sample file][workflow], and the value of the `on.push.branches` should be the same as your repo's default branch name. And then rename your repository to `<GH_USERNAME>.github.io` on GitHub.
2021-01-25 15:19:50 +03:00
2022-08-14 01:36:08 +03:00
Now publish your Jekyll site:
2021-01-25 15:19:50 +03:00
2022-08-14 01:36:08 +03:00
1. Browse to your repository on GitHub. Select the tab _Settings_, then click _Pages_ in the left navigation bar. Then, in the **Source** section (under _Build and deployment_), select [**GitHub Actions**][pages-workflow-src] from the dropdown menu.
2019-09-30 15:38:58 +03:00
2. Push any commit to remote to trigger the GitHub Actions workflow. In the _Actions_ tab of your repository, you should see the workflow _Build and Deploy_ running. Once the build is complete and successful, the site should be deployed automatically.
2019-09-30 15:38:58 +03:00
3. Visit your website at the address indicated by GitHub.
2022-01-11 13:33:05 +03:00
### Manually Build and Deploy
2019-09-30 15:38:58 +03:00
2021-09-29 15:44:00 +03:00
On self-hosted servers, you cannot enjoy the convenience of **GitHub Actions**. Therefore, you should build the site on your local machine and then upload the site files to the server.
2019-09-30 15:38:58 +03:00
2021-09-29 15:44:00 +03:00
Go to the root of the source project, and build your site as follows:
2019-09-30 15:38:58 +03:00
```console
2020-11-19 16:32:50 +03:00
$ JEKYLL_ENV=production bundle exec jekyll b
```
2021-09-29 15:44:00 +03:00
Or build the site on Docker:
2021-09-29 15:44:00 +03:00
```console
2020-11-19 16:32:50 +03:00
$ docker run -it --rm \
--env JEKYLL_ENV=production \
--volume="$PWD:/srv/jekyll" \
jekyll/jekyll \
2020-11-19 16:32:50 +03:00
jekyll build
2019-09-30 15:38:58 +03:00
```
2022-01-22 18:21:00 +03:00
Unless you specified the output path, the generated site files will be placed in folder `_site`{: .filepath} of the project's root directory. Now you should upload those files to the target server.
2021-09-29 15:44:00 +03:00
2022-01-11 13:33:05 +03:00
## Upgrading
2021-09-29 15:44:00 +03:00
It depends on how you use the theme:
2022-01-22 18:21:00 +03:00
- If you are using the theme gem (there will be `gem "jekyll-theme-chirpy"` in the `Gemfile`{: .filepath}), editing the `Gemfile`{: .filepath} and update the version number of the theme gem, for example:
2021-09-29 15:44:00 +03:00
2021-10-25 20:16:50 +03:00
```diff
2021-09-29 15:44:00 +03:00
- gem "jekyll-theme-chirpy", "~> 3.2", ">= 3.2.1"
+ gem "jekyll-theme-chirpy", "~> 3.3", ">= 3.3.0"
2021-10-25 20:16:50 +03:00
```
{: .nolineno file="Gemfile" }
2021-09-29 15:44:00 +03:00
2021-10-25 20:16:50 +03:00
And then execute the following command:
2021-09-29 15:44:00 +03:00
2021-10-25 20:16:50 +03:00
```console
$ bundle update jekyll-theme-chirpy
2021-10-25 20:16:50 +03:00
```
2021-09-29 15:44:00 +03:00
2021-10-25 20:16:50 +03:00
As the version upgrades, the critical files (for details, see the [Startup Template][starter]) and configuration options will change. Please refer to the [Upgrade Guide](https://github.com/cotes2020/jekyll-theme-chirpy/wiki/Upgrade-Guide) to keep your repo's files in sync with the latest version of the theme.
2021-09-29 15:44:00 +03:00
2022-01-22 18:21:00 +03:00
- If you forked from the source project (there will be `gemspec` in the `Gemfile`{: .filepath} of your site), then merge the [latest upstream tags][latest-tag] into your Jekyll site to complete the upgrade.
2021-09-29 15:44:00 +03:00
The merge is likely to conflict with your local modifications. Please be patient and careful to resolve these conflicts.
[starter]: https://github.com/cotes2020/chirpy-starter
[use-starter]: https://github.com/cotes2020/chirpy-starter/generate
[workflow]: https://github.com/cotes2020/jekyll-theme-chirpy/blob/master/.github/workflows/pages-deploy.yml.hook
2021-09-29 15:44:00 +03:00
[chirpy-4.1.0]: https://github.com/cotes2020/jekyll-theme-chirpy/releases/tag/v4.1.0
2022-09-10 12:23:20 +03:00
[pages-workflow-src]: https://docs.github.com/en/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site#publishing-with-a-custom-github-actions-workflow
2021-09-29 15:44:00 +03:00
[latest-tag]: https://github.com/cotes2020/jekyll-theme-chirpy/tags