A Go Web Eco-System
Go
Latest commit 8d897a9 Jan 21, 2017 @markbates markbates committed on GitHub Merge pull request #112 from gobuffalo/helpers/append-action-helper
First Attempt at #105
Permalink
Failed to load latest commit information.
buffalo fixed a broken test Jan 21, 2017
examples had to change the file resolvers work to make go.rice happy in binary Jan 4, 2017
grifts [grift] changing the task to be pointing the buffalo repo Jan 7, 2017
middleware Fix spelling mistake in PopTransaction documentation Jan 20, 2017
render Merge branch 'master' into pointers Jan 21, 2017
.codeclimate.yml Working on adding support for a Resource interface (#30) Dec 10, 2016
.csslintrc Working on adding support for a Resource interface (#30) Dec 10, 2016
.eslintignore Working on adding support for a Resource interface (#30) Dec 10, 2016
.eslintrc Working on adding support for a Resource interface (#30) Dec 10, 2016
.gitignore fixed up the examples to bring them more in line Dec 20, 2016
.travis.yml switch to using "latest" as the default docker go image Jan 13, 2017
CHANGELOG.md Updated changelog for release v0.7.1 Jan 13, 2017
Dockerfile switch to using "latest" as the default docker go image Jan 13, 2017
LICENSE.txt added a License Nov 24, 2016
README.md Minor spelling/grammar fixes Jan 19, 2017
SHOULDERS.md Minor spelling/grammar fixes Jan 19, 2017
app.go Edit some typo Jan 13, 2017
app_test.go added tests around using/skipping middleware Nov 23, 2016
context.go buffalo.Context should implement the context.Context interface close #… Jan 21, 2017
default_context.go buffalo.Context should implement the context.Context interface close #… Jan 21, 2017
default_context_test.go buffalo.Context should implement the context.Context interface close #… Jan 21, 2017
errors.go removing extraneous errors.WithStack call Jan 15, 2017
handler.go buffalo.Context should implement the context.Context interface close #… Jan 21, 2017
logger.go removed Warningf from the Logger Interface Dec 4, 2016
logo.svg added the svg logo to the archive Dec 20, 2016
method_override.go added an html-crud example to mirror the json-crud example. fixed a Dec 4, 2016
method_override_test.go moved to gobuffalo/buffalo Dec 29, 2016
middleware.go fixed an issue with skipping middleware for resource end points Jan 4, 2017
middleware_test.go fixed an issue with skipping middleware for resource end points Jan 4, 2017
multi_logger.go removed Warningf from the Logger Interface Dec 4, 2016
not_found.go Provide a mechanism to map status codes to error handles. Closes #110 Jan 12, 2017
not_found_test.go Provide a mechanism to map status codes to error handles. Closes #110 Jan 12, 2017
options.go Provide a mechanism to map status codes to error handles. Closes #110 Jan 12, 2017
request_logger.go improved the "stickiness" of the request_id in logs Jan 4, 2017
resource.go fixed an issue with skipping middleware for resource end points Jan 4, 2017
response.go added some helpers and event source support Dec 9, 2016
route.go Return the RouteInfo when mapping an endpoint. Also make it available in Jan 10, 2017
route_test.go proved what i wanted to with travis, fixing the tests again Dec 2, 2016
router.go Return the RouteInfo when mapping an endpoint. Also make it available in Jan 10, 2017
router_test.go working on moving to velvet Jan 4, 2017
session.go Add punctuation to be consistent Jan 8, 2017
wrappers.go more go doc Dec 2, 2016
wrappers_test.go working on #3 Nov 24, 2016

README.md

Buffalo GoDoc Build Status Code Climate Go Report Card

Buffalo is a Go web development eco-system. Designed to make the life of a Go web developer easier.

Buffalo starts by generating a web project for you that already has everything from front-end (JavaScript, SCSS, etc...) to back-end (database, routing, etc...) already hooked up and ready to run. From there it provides easy APIs to build your web application quickly in Go.

Buffalo isn't just a framework, it's a holistic web development environment and project structure that lets developers get straight to the business of, well, building their business.

I ❤️ web dev in go again - Brian Ketelsen

Documentation

Please visit http://gobuffalo.io for the latest documentation, examples, and more.

Installation

$ go get -u github.com/gobuffalo/buffalo/buffalo

Generating a new Project

Buffalo aims to make building new web applications in Go as simple as possible, and what could be more simple than a new application generator?

$ buffalo new <name>

That will generate a whole new Buffalo application that is ready to go. It'll even run go get for you to make sure you have all of the necessary dependencies needed to run your application.

To see a list of available flags for the new command, just check out its help.

$ buffalo help new

Running your application

Buffalo is Go "standards" compliant. That means you can just build your binary and run it. It's that simple.

Running your application in Development

One of the downsides to Go development is the lack of code "reloading". This means as you change your code you need to manually stop your application, rebuild it, and then restart it. Buffalo finds this is annoying and wants to make life better for you.

$ buffalo dev

The dev command will watch your .go and .html files by default, rebuild, and restart your binary for you so you don't have to worry about such things. Just run the dev command and start coding.

Testing your application

Just like running your application, Buffalo doesn't stop you from using the standard Go tools for testing. Buffalo does ship with a test command that will run all of your tests while conveniently skipping that pesky old ./vendor directory!

$ buffalo test

Shoulders of Giants

Buffalo would not be possible if not for all of the great projects it depends on. Please see SHOULDERS.md to see a list of them.

Templating

github.com/gobuffalo/velvet - This templating package was chosen over the standard Go html/template package for a variety of reasons. The biggest of which is that it is significantly more flexible and easy to work with. It also has the added factor of being familiar to those who have worked with "Handlebars" or "Mustache" templates before.

Routing

github.com/gorilla/mux - This router was chosen because of its stability and flexibility. There might be faster routers out there, but this one is definitely the most powerful!

Task Runner (Optional)

github.com/markbates/grift - If you're familiar with Rake tasks from Ruby, you'll be right at home using Grift. This package was chosen to allow for the easy running of simple, and common, tasks that most web applications need. Think things like seeding a database or taking in a CSV file and generating database records. Buffalo ships with an example routes task that prints off the defined routes and the function that handles those requests.

Models/ORM (Optional)

github.com/markbates/pop - Accessing databases is nothing new in web applications. Pop, and its command line tool, Soda, were chosen because they strike a nice balance between simplifying common tasks, being idiomatic, and giving you the flexibility you need to built your app. Pop and Soda share the same core philosphies as Buffalo so they were a natural choice.

Sessions, Cookies, Websockets, and more...

github.com/gorilla - The Gorilla toolkit is a great set of packages designed to improve upon the standard libary for a variety of web-related packages. With these high quality packages Buffalo is able to keep its "core" code to a minimum and focus on its goal of glueing them all together to make your life better.

Benchmarks

Oh, yeah, everyone wants benchmarks! What would a web framework be without its benchmarks? Well, guess what? I'm not giving you any! That's right. This is Go! I assure you that it is plenty fast enough for you. If you want benchmarks you can either a) checkout any benchmarks that the GIANTS Buffalo is built upon have published, or b) run your own. I have no interest in playing the benchmark game, and neither should you.

Contributors

  • Mark Bates
  • Antonio Pagano
  • Brian Downs
  • Cody Oss
  • arif emre
  • Mark Lussier
  • Kenny Grant