f81f9ceb40
FileAndExt has now be completely rewritten and now works as may reasonably be expected. The test cases for: ReplaceExtension Filename FileAndExt now all pass. The problem was the way path.Base was being used. Firstly Base returns "." if the directory is empty, but it can also return "." for the current directory, or ".." for the parent directory, if these are the last elements in the path. Simply detecting the presence of a "." in the returned string and truncating before the "." does not therefore always result in a valid filename. Secondly, Base strips any trailing slashes making is more difficult to detect when the path does not end in a filename but in a directory name i.e. a no filename case. Not detecting this incorrectly results in the last directory name being returned as the filename. The code has been updated to take account of of both situations so that: 1) An empty string for both the filename and extension is returned if the path does not contain a filename (plus an optional extension). This includes both the empty path case, and the ends in a directory case. 2) If the path represents a filename with an extension then both the filename and the extension (minus any dots) are returned as non empty strings. 3) If the path represents a filename without an extension then filename will be returned as a non empty string (minus any dot) and the extension will be returned as an empty string. |
||
|---|---|---|
| commands | ||
| create | ||
| docs | ||
| examples | ||
| helpers | ||
| hugofs | ||
| hugolib | ||
| livereload | ||
| parser | ||
| source | ||
| target | ||
| transform | ||
| utils | ||
| watcher | ||
| .gitignore | ||
| .travis.yml | ||
| baseline.txt | ||
| LICENSE.md | ||
| main.go | ||
| README.md | ||
| wercker.yml | ||
Hugo
A Fast and Flexible Static Site Generator built with love by spf13 and friends in Go.
Overview
Hugo is a static site generator written in Go. It is optimized for speed, easy use and configurability. Hugo takes a directory with content and templates and renders them into a full HTML website.
Hugo makes use of Markdown files with front matter for meta data.
A typical website of moderate size can be rendered in a fraction of a second. A good rule of thumb is that Hugo takes around 1 millisecond for each piece of content.
It is written to work well with any kind of website including blogs, tumbles and docs.
Complete documentation is available at Hugo Documentation.
Getting Started
Installing Hugo
Hugo is written in Go with support for Windows, Linux, FreeBSD and OS X.
The latest release can be found at hugo releases. We currently build for Windows, Linux, FreeBSD and OS X for x64 and i386 architectures.
Installing Hugo (binary)
Installation is very easy. Simply download the appropriate version for your platform from Hugo Releases. Once downloaded, it can be run from anywhere. You don't need to install it into a global location. This works well for shared hosts and other systems where you don't have a privileged account.
Ideally, you should install it somewhere in your path for easy use. /usr/local/bin
is the most probable location.
The Hugo executable has no external dependencies.
Installing from source
Dependencies
- Git
- Go 1.1+
- Mercurial
- Bazaar
Clone locally (for contributors):
git clone https://github.com/spf13/hugo
cd hugo
go get
Because Go expects all of your libraries to be found in either $GOROOT or $GOPATH, it's helpful to symlink the project to one of the following paths:
ln -s /path/to/your/hugo $GOPATH/src/github.com/spf13/hugoln -s /path/to/your/hugo $GOROOT/src/pkg/github.com/spf13/hugo
Get directly from GitHub:
If you only want to build from source, it's even easier.
go get -v github.com/spf13/hugo
Building Hugo
cd /path/to/hugo
go build -o hugo main.go
mv hugo /usr/local/bin/
Running Hugo
cd /path/to/hugo
go install github.com/spf13/hugo/hugolib
go run main.go
Contribution Guidelines
We welcome your contributions. To make the process as seamless as possible, we ask for the following:
- Go ahead and fork the project and make your changes. We encourage pull requests to discuss code changes.
- When you're ready to create a pull request, be sure to:
- Have test cases for the new code. If you have questions about how to do it, please ask in your pull request.
- Run
go fmt - Squash your commits into a single commit.
git rebase -i. It's okay to force update your pull request. - Make sure
go test ./...passes, and go build completes. Our Travis CI loop will catch most things that are missing. The exception: Windows. We run on Windows from time to time, but if you have access, please check on a Windows machine too.
Complete documentation is available at Hugo Documentation.
