Skip to content

EuphoriaCHN/Euphoria-Hexo

BranchesTags

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

85 Commits

scaffolds

scaffolds

 
 

scripts

scripts

 
 

source

source

 
 

themes/next

themes/next

 
 

.gitignore

.gitignore

 
 

LICENSE

LICENSE

 
 

README.md

README.md

 
 

_config.yml

_config.yml

 
 

build.sh

build.sh

 
 

db.json

db.json

 
 

package.json

package.json

 
 

Repository files navigation

Euphoria Blog

Euphoria Blog

Install

git clone git@github.com:EuphoriaCHN/Euphoria-Hexo.git
cd ./Euphoria-Hexo

npm install
npm run build
npm run serve

Dependencies

Node.js

Node.js is an open-source, cross-platform, JavaScript runtime environment. It executes JavaScript code outside of a browser. For more information on using Node.js, see the Node.js Website.

The Node.js project uses an open governance model. The OpenJS Foundation provides support for the project.

This project is bound by a Code of Conduct.

Table of Contents

Support

Looking for help? Check out the instructions for getting support.

Release Types

  • Current: Under active development. Code for the Current release is in the branch for its major version number (for example, v10.x). Node.js releases a new major version every 6 months, allowing for breaking changes. This happens in April and October every year. Releases appearing each October have a support life of 8 months. Releases appearing each April convert to LTS (see below) each October.
  • LTS: Releases that receive Long-term Support, with a focus on stability and security. Every even-numbered major version will become an LTS release. LTS releases receive 12 months of Active LTS support and a further 18 months of Maintenance. LTS release lines have alphabetically-ordered codenames, beginning with v4 Argon. There are no breaking changes or feature additions, except in some special circumstances.
  • Nightly: Code from the Current branch built every 24-hours when there are changes. Use with caution.

Current and LTS releases follow Semantic Versioning. A member of the Release Team signs each Current and LTS release. For more information, see the Release README.

Download

Binaries, installers, and source tarballs are available at https://nodejs.org/en/download/.

Current and LTS Releases

https://nodejs.org/download/release/

The latest directory is an alias for the latest Current release. The latest-codename directory is an alias for the latest release from an LTS line. For example, the latest-carbon directory contains the latest Carbon (Node.js 8) release.

Nightly Releases

https://nodejs.org/download/nightly/

Each directory name and filename contains a date (in UTC time) and the commit SHA at the HEAD of the release.

API Documentation

Documentation for the latest Current release is at https://nodejs.org/api/. Version-specific documentation is available in each release directory in the docs subdirectory. Version-specific documentation is also at https://nodejs.org/download/docs/.

Verifying Binaries

Download directories contain a SHASUMS256.txt file with SHA checksums for the files.

To download SHASUMS256.txt using curl:

$ curl -O https://nodejs.org/dist/vx.y.z/SHASUMS256.txt

To check that a downloaded file matches the checksum, run it through sha256sum with a command such as:

$ grep node-vx.y.z.tar.gz SHASUMS256.txt | sha256sum -c -

For Current and LTS, the GPG detached signature of SHASUMS256.txt is in SHASUMS256.txt.sig. You can use it with gpg to verify the integrity of SHASUM256.txt. You will first need to import the GPG keys of individuals authorized to create releases. To import the keys:

$ gpg --keyserver pool.sks-keyservers.net --recv-keys DD8F2338BAE7501E3DD5AC78C273792F7D83545D

See the bottom of this README for a full script to import active release keys.

Next, download the SHASUMS256.txt.sig for the release:

$ curl -O https://nodejs.org/dist/vx.y.z/SHASUMS256.txt.sig

Then use gpg --verify SHASUMS256.txt.sig SHASUMS256.txt to verify the file's signature.

Building Node.js

See BUILDING.md for instructions on how to build Node.js from source and a list of supported platforms.

Security

For information on reporting security vulnerabilities in Node.js, see SECURITY.md.

Contributing to Node.js

Current Project Team Members

For information about the governance of the Node.js project, see GOVERNANCE.md.

TSC (Technical Steering Committee)

TSC Emeriti

Collaborators

Collaborator Emeriti

Collaborators follow the COLLABORATOR_GUIDE.md in maintaining the Node.js project.

Release Keys

GPG keys used to sign Node.js releases:

To import the full set of trusted release keys:

gpg --keyserver pool.sks-keyservers.net --recv-keys 4ED778F539E3634C779C87C6D7062848A1AB005C
gpg --keyserver pool.sks-keyservers.net --recv-keys B9E2F5981AA6E0CD28160D9FF13993A75599653C
gpg --keyserver pool.sks-keyservers.net --recv-keys 94AE36675C464D64BAFA68DD7434390BDBE9B9C5
gpg --keyserver pool.sks-keyservers.net --recv-keys B9AE9905FFD7803F25714661B63B535A4C206CA9
gpg --keyserver pool.sks-keyservers.net --recv-keys 77984A986EBC2AA786BC0F66B01FBB92821C587A
gpg --keyserver pool.sks-keyservers.net --recv-keys 71DCFD284A79C3B38668286BC97EC7A07EDE3FC1
gpg --keyserver pool.sks-keyservers.net --recv-keys FD3A5288F042B6850C66B31F09FE44734EB7990E
gpg --keyserver pool.sks-keyservers.net --recv-keys 8FCCA13FEF1D0C2E91008E09770F7A9A5AE15600
gpg --keyserver pool.sks-keyservers.net --recv-keys C4F0DFFF4E8C1A8236409D08E73BC641CC11F4C8
gpg --keyserver pool.sks-keyservers.net --recv-keys DD8F2338BAE7501E3DD5AC78C273792F7D83545D
gpg --keyserver pool.sks-keyservers.net --recv-keys A48C2BEE680E841632CD4E44F07496B3EB3C1762

See the section above on Verifying Binaries for how to use these keys to verify a downloaded file.

Other keys used to sign some previous releases:

Hexo logo

Hexo

A fast, simple & powerful blog framework, powered by Node.js.

Website | Documentation | Installation Guide | Contribution Guide | Code of Conduct | API | Twitter

NPM version Required Node version Build Status Build status dependencies Status devDependencies Status Coverage Status Gitter Discord Chat Telegram Chat FOSSA Status Contributor Covenant

Features

  • Blazing fast generating
  • Support for GitHub Flavored Markdown and most Octopress plugins
  • One-command deploy to GitHub Pages, Heroku, etc.
  • Powerful API for limitless extensibility
  • Hundreds of themes & plugins

Quick Start

Install Hexo

$ npm install hexo-cli -g

Setup your blog

$ hexo init blog
$ cd blog

Start the server

$ hexo server

Create a new post

$ hexo new "Hello Hexo"

Generate static files

$ hexo generate

More Information

Contributing

We welcome you to join the development of Hexo. Please see contributing document. 🤗

Also, we welcome PR or issue to official-plugins.

Contributors

Backers

Backers

Sponsors

JetBrains

CMS Critic

Getform

License

FOSSA Status

Language: 🇺🇸 🇨🇳 🇷🇺

e x T

«NexT» is a high quality elegant Hexo theme. It is crafted from scratch with love.



Live Preview

💟 Muse | 🔯 Mist | ♓️ Pisces | ♊️ Gemini

More «NexT» examples here.

Installation

The simplest way to install is to clone the entire repository:

$ cd hexo
$ git clone https://github.com/theme-next/hexo-theme-next themes/next

Or you can see detailed installation instructions if you want any other variant.

Plugins

In NexT config now you can find dependencies on each module which was moved to external repositories which can be found by main organization link.

For example, if you want to enable pjax on your site, go to NexT config and see:

# Easily enable fast Ajax navigation on your website.
# Dependencies: https://github.com/theme-next/theme-next-pjax
pjax: false

Then turn on pjax and go to «Dependencies» link with installation instructions of this module.

Configure CDN

If you use CDN for any plugins, you need to replace your CDN link.

For example, if you want to use mediumzoom and you configured a CDN link, go to NexT config and see:

vendors:
  # ...
  # Some contents...
  # ...
  mediumzoom: # Set or update mediumzoom CDN URL.

Instead of defining main organization link for updates.

Update

You can update to latest master branch by the following command:

$ cd themes/next
$ git pull

And if you see any error message during update (something like «Commit your changes or stash them before you can merge»), recommended to learn Hexo data files feature.
However, you can bypass update errors by using the Commit, Stash or Reset commands for local changes. See here how to do it.

If you want to update from v5.1.x to the latest version, read this.

Feedback

Contributing

We welcome you to join the development of NexT. Please see contributing document. 🤗

Also, we welcome Issue or PR to official-plugins.

Contributors

Thanks

«NexT» send special thanks to these great services that sponsor our core infrastructure:

   

GitHub allows us to host the Git repository, Netlify allows us to distribute the documentation.



Crowdin allows us to translate conveniently the documentation.

   

Codacy allows us to monitor code quality, Travis CI allows us to run the test suite.

About

博客同步文件

Resources

Readme

License

MIT license
Activity

Stars

0 stars

Watchers

2 watching

Forks

0 forks
Report repository

Releases

No releases published

Packages

No packages published

Languages