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

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

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











To download projects locally via Git, follow these steps: Install Git. Navigate to the project directory. cloning the remote repository using the following command: git clone https://github.com/username/repository-name.git

Steps to update git code: Check out code: git clone https://github.com/username/repo.git Get the latest changes: git fetch merge changes: git merge origin/master push changes (optional): git push origin master

In order to securely connect to a remote Git server, an SSH key containing both public and private keys needs to be generated. The steps to generate an SSH key are as follows: Open the terminal and enter the command ssh-keygen -t rsa -b 4096. Select the key saving location. Enter a password phrase to protect the private key. Copy the public key to the remote server. Save the private key properly because it is the credentials for accessing the account.

To fall back a Git commit, you can use the git reset --hard HEAD~N command, where N represents the number of commits to fallback. The detailed steps include: Determine the number of commits to be rolled back. Use the --hard option to force a fallback. Execute the command to fall back to the specified commit.

Git is a version control system, and GitHub is a Git-based code hosting platform. Git is used to manage code versions and supports local operations; GitHub provides online collaboration tools such as Issue tracking and PullRequest.

Git code merge process: Pull the latest changes to avoid conflicts. Switch to the branch you want to merge. Initiate a merge, specifying the branch to merge. Resolve merge conflicts (if any). Staging and commit merge, providing commit message.

To view the Git repository address, perform the following steps: 1. Open the command line and navigate to the repository directory; 2. Run the "git remote -v" command; 3. View the repository name in the output and its corresponding address.

Resolve: When Git download speed is slow, you can take the following steps: Check the network connection and try to switch the connection method. Optimize Git configuration: Increase the POST buffer size (git config --global http.postBuffer 524288000), and reduce the low-speed limit (git config --global http.lowSpeedLimit 1000). Use a Git proxy (such as git-proxy or git-lfs-proxy). Try using a different Git client (such as Sourcetree or Github Desktop). Check for fire protection
