Go Web Examples

https://gowebexamples.github.io/

by adamnemecek • 9 years ago

357 90 9 years ago

gowebexamples.github.io

tlow2• 9 years ago

Why put "<li><s>" and "</s></li>" in the html file? Given your style you should clearly abstract this out static HTML.

Edit: update. Odd that people are upvoting and downvoting this comment.

nkozyra• 9 years ago

Possibly because the underlying HTML is not really the point of the tutorial.

tlow2• 9 years ago

In web examples HTML is "not really the point"? Ok. I can actually accept that as reasonable. But isn't the style of this example to abstract static HTML out of the HTML file and generate it dynamically as needed? I'll grant that it's a rather small issue; nonetheless, I do think the author would be best served by said abstraction for style and consistency (to the last detail).

adamnemecek2• 9 years ago

Actually the link should be to https://gowebexamples.github.io/ I screwed up when posting this lol.

dang• 9 years ago

Ok, we changed to that from https://gowebexamples.github.io/templates/.

azinman2• 9 years ago

Fantastic. I've found previous examples hard to get into... either way too complex, not doing enough, or not structured well. Thank you!

Update: 2 requests: http/2, and https (self-signed, with chained cert, and mutual auth)

sherlockgopher3• 9 years ago

I found this to be a good source, https://github.com/thewhitetulip/web-dev-golang-anti-textboo...

resist_futility• 9 years ago

another set of examples https://gist.github.com/denji/12b3a568f092ab951456

bharani_m• 9 years ago

I am interested in trying out Go for my next side project. Can anyone recommend any good books/videos that can help me get started?

wwalser• 9 years ago

This is how I got started: https://tour.golang.org/welcome/1

Work through those followed by a few project Euler challenges then implement something simple in the domain that you normally work in. For me that's web so I implemented a little HipChat bot.

spraak• 9 years ago

The Go Programming Language (https://gopl.io) is what I've had at my desk the past few weeks while learning. Also whenever I get stuck I search Github code for a term like "json.Unmarshal" to find how others have done something. And otherwise just duckduckgo'ing "golang <search term>". Also you'll hear a million times to check out Effective Go and The Go Tour (on the official Golang site). Those are good but I appreciate them more now that I've got a good foundation

smt923• 9 years ago

This is one of the things that most stood out with me while I was learning Go, it's just so easy to read other people's examples and just understand it without too much hard thought

beliu• 9 years ago

Another great resource for getting started is https://gobyexample.com/.

Also check out usage examples on Sourcegraph (disclaimer: I'm the CTO). We sell our tool to companies to use on their private code, but a side effect is that we've indexed usage examples for just about every popular Go open-source library. For example,

- Go std lib http package: https://sourcegraph.com/github.com/golang/go@bb41b4d599f5758...

- Popular gorilla/mux routing library: https://sourcegraph.com/github.com/gorilla/mux@34bf6dc9faa08...

- Gorp, a popular ORM-ish library: https://sourcegraph.com/github.com/go-gorp/gorp@033bf796a22f...

Cross-repo jump-to-def + find-references = great for making sense of new code.

sethammons2• 9 years ago

I would replace gorp with https://github.com/vattle/sqlboiler. Granted, I've not used either, but I like the philosophy behind sqlboiler. I feel it is more in line with Go principles. I also believe gorp will have issues with the new DB context stuff (though I'm not positive on that).

adamnemecek2• 9 years ago

I know this isn't a book but if you need a go development environment, cloud9 (https://c9.io) ended up being a surprisingly productive environment. Like for go development, it's been better than anything I've tried to setup locally and the IDE even has go autocomplete.

sherlockgopher3• 9 years ago

These might be helpful

Tutorial: https://github.com/thewhitetulip/web-dev-golang-anti-textboo...

YouTube series: https://www.youtube.com/playlist?list=PL41psiCma00wgiTKkAZwJ...

weberc2• 9 years ago

In particular, if you have any problems, /r/golang is very helpful. They'll help get you unstuck quickly.

timdeneau• 9 years ago

Todd McLeod has a good introductory series, with lots of follow along examples.

https://www.youtube.com/channel/UCElzlyMtkoXaO3kFa5HL0Xw

joncalhoun4• 9 years ago

If you want to ping me with what you are looking to build and your programming experience level I can recommend more specific resources. jon [at] calhoun.io

Many resources (like my book) are targeting absolute beginners so they are a bit lengthier to read if you are experienced, whereas other great books and whatnot are really hard for beginners to follow so at least expressing your skill level would help me recommend specific resources.

pkulak• 9 years ago

Love the way that library handles websockets. Perfect example of the way Go tends to work: no magic at all, yet it's also simple, concise and elegant.

gempir• 9 years ago

This is awesome. Examples are so important when learning something and I always found it hard to get good Go web examples

sherlockgopher3• 9 years ago

This might be helpful!

Tutorial: https://github.com/thewhitetulip/web-dev-golang-anti-textboo...

YouTube series: https://www.youtube.com/playlist?list=PL41psiCma00wgiTKkAZwJ...

ilozinski• 9 years ago

Gorilla mux is way overrated and overused. I'm not sure why it's the first choice for so many people. There are much better alternatives such as https://github.com/julienschmidt/httprouter or https://github.com/gin-gonic/gin.

Arcaire• 9 years ago

Care to explain why it's overused in comparison to other toolkits/frameworks/libraries? Taking in to account, of course, the target use-cases.

AsyncAwait• 9 years ago

Part of the reason is that gorilla/mux uses identical API to the standard library.

iamgopal• 9 years ago

Contradiction does not exist. :)

sethammons2• 9 years ago

I avoid httprouter because it doesn't adhere to the standard library interface for http handlers. I've not used gin, but it looks to also not follow the standard library interface here. Also, it does not appear to make use of newer developments in Go such as the context package (it imports the x/pkg version but does nothing with it I think).

joncalhoun4• 9 years ago

I believe gorilla mux came out years before the others, so it's not really shocking that it is used more. I personally have never had any issues with it but to each there own.

mmgutz• 9 years ago

Along the same tone, httprouter doesn't allow defining these routes simultaneously

    users/:id
    users/watching

Was kind of surprised as we have many routes like that. Like gorilla/mux, I think it was just first (trie-based mux). Isn't gin based on httprouter?

There are even better muxes now. `pressly/chi` is used by heavy hitters in production and takes advantage of Go 1.7 HTTP context. `labstack/echo` is another highly recommended by others but I don't like the non-idiomatic echo.Context in handler signatures.

Back on topic, I hope the go web examples only imports built-in packages. The gorilla/mux example could easily be written to use built-in packages.

jhoechtl• 9 years ago

I am currently searching for an example / skeleton in Go where I can upload a file via the browser to the server (drag and drop added bonus). Any examples?

lesiki• 9 years ago

I don't know much about Go so can't speak to the server-side handling of file uploads. The drag/drop side of things is server agnostic - I strongly recommend http://www.dropzonejs.com

merlish• 9 years ago

I actually wrote an extremely shonky/basic file upload thing and contributed it to the weird 'illacceptanything' repository, while that was a thing, about a year and a half ago.

Maybe you'll find it helpful, maybe not. Ignore the bindata.go stuff and look at main.go (inc. file accepting) & the file upload control (w/Bootstrap fileinput.min.js) & the braindead simple HTML templating stuff.

https://github.com/leafi/illacceptanything/commit/1b78922f89...

lentil• 9 years ago

This might be more of a complete app than you need, but https://transfer.sh is open source and it looks fairly compact. Could be some interesting examples in there?

Spiritus• 9 years ago

Something like this will hopefully get the point across on how to handle "multipart/form-data" forms. It will print the content of the upload to the server's stdout.

https://play.golang.org/p/DiNGdl27kE

You can use curl to test it out (it assumes a file called "foobar.txt" is available):

    curl -v -F upload=@foobar.txt localhost:8080/upload

bitexploder2• 9 years ago

I really like the gophish app for easy to understand common patterns in web apps.

mreithub• 9 years ago

Has anyone of you experience with the fasthttp Go library[0]?

Does it keep its promise in terms of speed? (I assume real world code would spend much more time in actual business logic than their examples/benchmarks so I guess there wouldn't be as much a difference as they claim, but the idea of zero allocations intrigues me)

[0] https://github.com/valyala/fasthttp

grey-area5• 9 years ago

It doesn't support http2.

tscs37• 9 years ago

The fasthttp library is good if you don't need to support corner cases of HTTP and you don't need HTTP/2.

If that is given, yes, it's faster.

daenney• 9 years ago

If you want HTTP/2 support Chi[0] can probably help. It's plenty snappy too.

[0] https://github.com/pressly/chi

sagichmal• 9 years ago

I don't recommend it; it doesn't actually implement HTTP, and the stdlib package net/http is extremely fast on its own.

petepete2• 9 years ago

These look great, thanks. I'm currently learning Go and find this kind of example much easier to follow than documentation.

I'd like to see an example for embedding HTML templates properly. It took me an embarrassing amount of time to get beyond 'header.html' and 'footer.html' being separate, and I'm sure my solution isn't as elegant as it could be.

joncalhoun4• 9 years ago

Is https://www.calhoun.io/creating-the-v-in-mvc/ close to what you had in mind?

I need to do a follow-up to that with the type I use to wrap that logic, but I am curious if this is inline with what you are looking for in the examples.

petepete2• 9 years ago

Yes, thank you. My solution was similar but less elegant; I plan on going through your post in more depth and attempt to reimplement my code with what I've learned.

Once again, thank you for that post.

Shanea93• 9 years ago

This is great, really simple and easy to follow examples.

Would you be able to add some other examples such as interfacing with a database or making remote network requests over http?

blackss2• 9 years ago

If you wanna simple database utility for testing golang db conn, please check https://github.com/blackss2/utility/blob/master/README.md

go get github.com/blackss2/utility/convert * don't use for production

elmacho392• 9 years ago

As always (not go specific), forms example is missing form validation. Is that too old-fashioned?

fallenhitokiri• 9 years ago

What kind of validation are you looking for? Simple things like "is not empty", "maximum 8 characters"...?

Most libraries I've seen which try to do form validation always lack in certain areas or force you to define your own validation, so I simply ended up adding an `isValid` method to my structs.

elmacho392• 9 years ago

I want to see a full roundtrip:

1. define input fields in html template of choice

2. validate form/struct/whatever and prepare errror messages per field

3. redisplay html with field-level errors to let user correct its input

step 3. is the interesting and missing in most examples of newer webframeworks

jchannon• 9 years ago

Go Content Negotiation - https://github.com/jchannon/negotiator

StevePerkins3• 9 years ago

It seems like there are three classes of "web problems" to solve:

(1) The absolute basic "hello world" stuff at the outset. How to route URL's to their handlers, how to render dynamic templates, how to map data structures to and from JSON, etc.

(2) The problems that are one level up in sophistication, but still common to nearly all web apps. How to handle authentication (username/pass, OAuth/JWT, etc), how to manage session state or the lack thereof, juggling synchronous blocking operations with async background ones, etc.

(3) Really advanced issues that are probably specific to your industry domain or specific application, and aren't necessarily common to others (e.g. how to isolate this medical data for HIPPA compliance).

I don't want to poo-poo this website, it's nice. But in my mind, the world is already flooded with Category #1 examples. At the same time, Category #3 doesn't really lend itself to this sort of thing at all. So what the world really needs is more Category #2 stuff.

Example: What are the patterns available for authentication, including their advantages and drawbacks?

If you do your own authentication with usernames and passwords... then you have to either have to pass them every time and re-auth every request, or else store a session cookie on the client side and find some way share it across all your server-side instances (or use a load balancer with sticky sessions). That's material for 3 or 4 patterns right there!

If you use OAuth with JWT tokens, then you can (maybe) avoid the need to store any session state on the server side. But how do you explicitly "logout" prior to the JWT expiration? Another 3 or 4 patterns down this route!

Category #1 is fun and easy to write about, and a lot af that material comes from newbies who are writing in order to teach themselves. But Category #2 is the brick wall that people always run into in the real world... and because you need a lot of real experience to write about that class of problems, there's a vacuum of available material out there.

tptacek8• 9 years ago

Apart from the JWT thing (please avoid JWT if possible), I agree with this comment 100%. Things I'd like to see in a Go web app example site:

1. Examples of using context values to pass things selectively to handlers.

2. An arbitrary trivial middleware example, like a specialized request logger, just to demonstrate Go middleware.

3. A Rails/Django-style session token done in the same middleware style.

4. Giving requests a notion of "current user".

5. Simplified user-visible vs. developer-visible error handling.

It's too much to ask for ORM-style database query examples, I know, but that too would be nice.

jankiel• 9 years ago

Can you expand on JWT thing? Why should it be avoided?

StevePerkins3• 9 years ago

please avoid JWT if possible

That's why this Category #2 stuff is so important. People can agree without much controversy what "best practice" is for the Category #1 stuff, but at the next level it's just blog posts and discussion thread comments passionately arguing opposite statements.

I'm curious... if not JWT, then how would you approach the problem of authenticated sessions without server-side state? (assuming you aren't rejecting the overall premise entirely)

If you track authentication with a server-side session, then you have to either:

(1) Setup a backing store for your session state (e.g. Redis, relational database, proprietary app server solution, etc). Share the backing store across all instance nodes in your server-side cluster. Tune the inevitable performance issues and point-of-failure risks, and expect the worst if you're using a proprietary thing (they're all terrible).

(2) Use a hardware solution. Have the load balancer always route a given client's requests to the same server-side instance. Deal with failover scenarios when that instance goes down, have to drain traffic every time you want to do a deployment, etc.

JWT's ugly, but no uglier than either of those! Always on the lookout for other recipes...

brightball2• 9 years ago

Totally agree. It's because of stuff like this that I find Go to be fairly tedious for full stack web. JSON microservice that's blazing fast is great. High concurrency workload, great.

Full stack website that reuses template parts with live data, manages sessions and logins, images, JavaScript and CSS...not so much.

d01002• 9 years ago

Why avoid JWT? Has there been some new development regarding it that makes it unsuitable for auth? I just started using it in a new app...

bitexploder2• 9 years ago

Sort of funny, that is more or less exactly the stuff we needed for our internal candidate assessment app built on go/http. It just makes sense and is stuff you will want in any app, even a mostly CRUD one.

FWIW, gophish is a very clean app built using Gorilla packages that implements these patterns in a comprehensible way and I found it very helpful as I was implementing things.

joncalhoun4• 9 years ago

Your first request is tricky because it can lead to issues down the road if done poorly, so it is hard to just give a quick example of it. I wrote about this subject recently (see https://www.calhoun.io/pitfalls-of-context-values-and-how-to... ) and there is a lot of info to cover. That said I could see value in doing an example and referencing a more in depth overview from the example.

Once you cover (1) most of the others fall into line. There is little reason to use context values outside of MW from my experience.

Re (3) - can you provide a link or example of what you mean?

(5) - again, can you elaborate? Are you referring to error types? Or just how the errors are rendered?

I ask all these questions because I write a lot about Go and I am interested in trying to make examples of these available, but I want to understand what you are asking for first.

omginternets2• 9 years ago

Anybody have experience with Echo? [0]

[0] https://echo.labstack.com/

nathancahill2• 9 years ago

Yes, I use it for several microservices, running for about a year now in prod. It's excellent.

omginternets2• 9 years ago

It seems very nice indeed.

Thanks for the feedback.

amelius• 9 years ago

This example will show how to register a route and get the data using just the net/http package.

What is a "route"?

(I don't need an answer, but I think the example should explain it).

nnd• 9 years ago

Why would I want use Go for the backend, rather than a Python or Node.js framework? Just looking at the syntax it strikes me how inconcise and it is.

falcolas• 9 years ago

Just looking at the syntax it strikes me how inconcise and it is.

And you recommend Javascript instead? Interesting.

Why would I want use Go for the backend

Fast, built-in concurrency, enough high level concepts and structures to support fast development, and really easy to deploy.

The last part is probably the greatest. It supports simple host-based deploys, tiny docker container deploys, and eliminates the typical dependency conflict problems of Python and Node.

It's also pragmatic enough to make it easy to develop in for developers across the skill bell curve.

simplyluke• 9 years ago

In general: more performant, much better at threading through goroutines. It's worth noting go is compiled, so it's more comparable to a language like C++ than a dynamic language like python or JS.

my_ghola• 9 years ago

I haven't tried Go in a while but I see a lack of error handling in the code examples. Is that just to keep the code simple? I'd rather see examples with best practice handling of errors. Maybe show both versions so readers can see the difference?

hit8run• 9 years ago

These guides go into the right direction. I solved many things for myself but it would be nice to collect good practices. I had to come up with go style design patterns for: - Middlewares - Authentication - Authorization - Database Access - JSON APIs - Template organization - Migrations - i18n - Crypted Cookies - Image uploading - Form validation - Asset Pipeline - API Versioning - Writing libs for 3rd party services Where is the best place to share my best practices and to discuss them with others? Via a pull request to that repo? You know of other good sources?

Go Web Examples

Related Stories