How to deploy hexo to gitee
With the development of the times and the increasing popularity of the Internet, personal blogs have become an existence that cannot be ignored. As more and more people choose to use the Hexo framework to build their own blog websites, how to deploy Hexo to Gitee has become a hot topic.
Gitee is a domestic code hosting platform with stable servers and fast access speeds. It also provides many commonly used functions, including Git code hosting, Wiki, Issues, etc., which can better meet the needs of Developer needs.
First, we need to create a warehouse on Gitee to store our Hexo blog site. Click the "New Warehouse" button on the Gitee homepage, fill in the relevant information, and choose to create an empty warehouse.
Next, we need to install Hexo locally. First, you need to ensure that the Node.js environment has been installed, then open the command line tool and enter the following command to install Hexo:
npm install -g hexo-cli
After the installation is completed, we can use the following command to create a new Hexo blog site:
hexo init blog cd blog npm install
The above command creates a folder named "blog", which contains a basic Hexo blog site. Then we need to push the site to Gitee. Enter the following command in the command line tool:
git init git add . git commit -m "first commit" git remote add origin git@gitee.com:username/blog.git git push -u origin master
where username is your Gitee username and needs to be replaced with the actual username. The above command completes the operation of pushing the local Hexo blog site to the Gitee repository.
However, we noticed that the directory structure on the Gitee repository does not meet the requirements of the Hexo blog site. In order to solve this problem, we need to execute the following commands in the local Hexo blog site:
hexo clean hexo generate
These commands will delete the local cache files and generate a complete site folder. Then, we need to push the folder to the Gitee repository.
First, we need to create a new .gitignore file in the blog directory to exclude some unnecessary files. Add the following content to the file:
.DS_Store Thumbs.db db.json *.log node_modules/ public/ .deploy*/
This excludes some files automatically generated by Hexo and some files that do not need to be uploaded to Gitee. Then, we execute the following commands in sequence:
npm install hexo-deployer-git --save hexo deploy
After executing the above commands, Hexo will push the blog site to the Gitee warehouse and deploy it automatically. We can find the corresponding page address in the "Settings" of the Gitee repository and access it in the browser.
Note that if you are prompted to enter a username and password when performing a deployment operation, we need to change the address of the Gitee warehouse to HTTPS format and execute the following command on the command line:
git remote set-url origin https://gitee.com/username/blog.git
Above The command changes the address of the Gitee repository to HTTPS format, which can avoid the need to enter the user name and password during deployment.
To sum up, deploying Hexo to Gitee is not complicated. You only need to follow the above steps to complete. In this way, we can easily host our personal Hexo blog site on Gitee and share it with more readers.
The above is the detailed content of How to deploy hexo to gitee. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



GitHub is not difficult to learn. 1) Master the basic knowledge: GitHub is a Git-based version control system that helps track code changes and collaborative development. 2) Understand core functions: Version control records each submission, supporting local work and remote synchronization. 3) Learn how to use: from creating a repository to push commits, to using branches and pull requests. 4) Solve common problems: such as merge conflicts and forgetting to add files. 5) Optimization practice: Use meaningful submission messages, clean up branches, and manage tasks using the project board. Through practice and community communication, GitHub’s learning curve is not steep.

Git and GitHub are not the same thing. Git is a version control system, and GitHub is a Git-based code hosting platform. Git is used to manage code versions, and GitHub provides an online collaboration environment.

Microsoft does not own Git, but owns GitHub. 1.Git is a distributed version control system created by Linus Torvaz in 2005. 2. GitHub is an online code hosting platform based on Git. It was founded in 2008 and acquired by Microsoft in 2018.

On your resume, you should choose to write Git or GitHub based on your position requirements and personal experience. 1. If the position requires Git skills, highlight Git. 2. If the position values community participation, show GitHub. 3. Make sure to describe the usage experience and project cases in detail and end with a complete sentence.

Starting from Git is more suitable for a deep understanding of version control principles, and starting from GitHub is more suitable for focusing on collaboration and code hosting. 1.Git is a distributed version control system that helps manage code version history. 2. GitHub is an online platform based on Git, providing code hosting and collaboration capabilities.

Git is an open source distributed version control system that helps developers track file changes, work together and manage code versions. Its core functions include: 1) record code modifications, 2) fallback to previous versions, 3) collaborative development, and 4) create and manage branches for parallel development.

The reason for using GitHub to manage HTML projects is that it provides a platform for version control, collaborative development and presentation of works. The specific steps include: 1. Create and initialize the Git repository, 2. Add and submit HTML files, 3. Push to GitHub, 4. Use GitHubPages to deploy web pages, 5. Use GitHubActions to automate building and deployment. In addition, GitHub also supports code review, Issue and PullRequest features to help optimize and collaborate on HTML projects.

GitLab is better for some developers and teams because it provides a complete DevOps toolchain and powerful CI/CD capabilities. 1. GitLab's CI/CD function is integrated within the platform, supporting full process automation from code submission to deployment. 2. Its server-side rendering technology improves page loading speed for large projects. 3. GitLab's permission management system is more flexible and supports fine-grained control.
