mirror of https://gitlab.com/curben/blog
5.7 KiB
5.7 KiB
title | date | tags |
---|---|---|
How to create a Hexo blog | 2018-09-21 00:00:00 |
Create a website/blog (hosted by GitLab for free) using the following guide:
GitLab project
- Register a free GitLab account or use your current one.
- Fork this project.
- Shared Runners should be enabled. Go to your (forked) project
Settings -> CI / CD -> Shared Runners
. - Change project website to a user website. This is so that the website's home page is
<your-username>.gitlab.io/
, instead of<your-username>.gitlab.io/hexo
. Go toSettings -> General -> Advanced -> Rename repository
. Change the Path to<your-username>.gitlab.io
. - You can start writing a new post straightaway without installing Hexo. You still need to change the blog's name and favicon though (how-to.
- To create a new post (through GitLab.com), create a new
<post-title>.md
file insource/_posts
folder. - Start with the following header/front-matter:
--- title: Test page date: yyyy-mm-dd hh:mm:ss tags: categories: ---
- To create a new post (through GitLab.com), create a new
- After you create a new post, the website can be accessed on
<your-username>.gitlab.io/
or the link shown on your projectSettings -> Pages
.
Installation
- Having Hexo means you can debug locally, rather than waiting for CI. You can even run a local server to preview your blog (see step 6 below).
- Clone this project to your workstation. Change
<folder>
to a preferred name.
$ git clone https://gitlab.com/curben/curben.gitlab.io <folder>
# Installing npm will also install nodejs as dependency.
# Ubuntu 16.04 or newer
$ sudo snap install node --classic --channel=10
# Debian
$ curl -sL https://deb.nodesource.com/setup_10.x | sudo -E bash -
$ sudo apt-get install -y nodejs
# Fedora 29
$ sudo dnf install npm
# Fedora 28 or older
$ curl --silent --location https://rpm.nodesource.com/setup_10.x | sudo bash -
$ sudo yum -y install nodejs
# Arch Linux
$ sudo pacman -S npm
- Install Hexo and its dependencies (defined in
package.json
). Re-launch the terminal program before continue.
$ cd <folder>
$ sudo npm install -g hexo-cli
$ npm install
- Generate static files to check for any error. You should always do this before pushing/merging commits to the
master
branch.
$ hexo generate
- (Optional) Start Hexo server on localhost:4000 to preview the blog. (more info)
$ npm install hexo-server --save
$ hexo server
- Commit the changes and push them. The generated
public
andnode_modules
are ignored, as CI will generate them during build. - Check the build status by going to your project
CI /CD -> Pipelines
. Due to the limitation ofhexo
, the build will always pass even when there is error. Check the Jobs log, look for any error after$ hexo deploy
. - If there is no error, the generated website can be accessed on
<your-username>.gitlab.io/
or the link shown on your projectSettings -> Pages
.
Writing
- Create a new post (using Hexo)
$ hexo new "My New Post"
My-New-Post.md
is created to thesource/_posts
folder, with the following header/front-matter:
---
title: My New Post
date: yyyy-mm-dd hh:mm:ss
tags:
categories:
---
To create a new page or more info: Writing
Configuration
Naming
Change the website's author and name
_config.yml
:
title:
subtitle:
description:
author:
themes/typing/_config.yml
:
menu:
GitLab: <your-gitlab-project-link>
# Customize /about page
nickname:
description:
Favicon
RealFaviconGenerator provides a web-based tool to generate favicons with wide compatibility.
- Upload your favicon (at least 260x260) and configure however you want.
- Install the generated package to
themes/typing/source
folder. Make you replace all existing files. - Edit
themes/typing/layout/_partial/head.ejs
. Change thecolor
values ofmask-icon
andmsapplication-TileColor
to the values you configured on the generator. - Check for any error using
hexo generate
(you should do this before you push any commit). - Commit and push.
- Check your favicon with the favicon checker.
Project page
If you prefer to have a project page on GitLab:
- go to
Settings -> General -> Advanced -> Rename repository
. Change the Path to<directory>
, so the website is available at<your-username>.gitlab.io/<directory>
,<directory>
can be any name, likeblog
orhexo
. - Edit
_config.yml
, change theroot:
value from""
to"/<directory>/"
. - Commit and push.
Remove fork relationship
If you don't have any plan to send merge requests to the upstream, you can remove fork relationship permanently by going to Settings -> General -> Advanced -> Remove fork relationship
.