4 ms·
How about http://gohugo.io/ http://gohugo.io/ ?
by primroot 12y ago
How about http://gohugo.io/ http://gohugo.io/ ?
- josephernest 12y agoLooks nice but when I click "Install" on home page of gohugo.io, I see: "brew install hugo". Another tool that I don't know: "brew", and that I probably cannot install on my shared hosting server. The point of Void is minimalism: apache+php, nothing else required. < 100 lines of code in a single php file (+ the markdown parser lib of course).
- krat0sprakhar 12y agoHugo is a static site generator much more fully featured than Void, so IMO its not fair to compare on LOC. As far as brew goes, that is just for convenience. You can might as well download the static binary from the releases page - https://github.com/spf13/hugo/releases https://github.com/spf13/hugo/releases
- frio 12y agoImmediately above that it has a big button that says "Download", which takes you here (https://github.com/spf13/hugo/releases https://github.com/spf13/hugo/releases). Above the `brew install hugo` part, it asks "Using Homebrew?", implying that option is for people already using that tool. I definitely agree that less complexity is better, but I think levelling that complaint against (this part of) Hugo is unfair.
- epimetheus 12y agoI believe the CMS should build on your local machine and then be pushed to your hosting after it builds the static files. Like Jekyl. That's how I'm reading it, and brew references Homebrew, an OSX package manager.
- blumkvist 12y agouhm... you don't need brew to install Hugo. It's an option.
- nosefrog 12y agoHow far along is hugo? I tried and failed to make the blog I wanted with it and had to hack around its deficiencies. I appreciate the fact that it's a single static binary, but its directory structure is overly complicated and arbitrary things don't work.