tour: Rename mux -> mu to follow convention

Nearly all sync.Mutex members in the standard library are named mu,
or use "mu" as part of the name. While this isn't a documented
recommendation anywhere that I can find, it would seem nice to start
new users with this same convention.

Change-Id: I67cbe2a0052b81d8bb57d5ece0cefd2f3838f298
GitHub-Last-Rev: 31ef869d9b72e7eb08b9be9340242b0e535a175f
GitHub-Pull-Request: golang/tour#813
Reviewed-by: Brad Fitzpatrick <>
1 file changed
tree: e5353ca89cd810368f60014fc40523ddd7e0ef8a
  1. .gcloudignore
  7. TODO
  9. app.yaml
  10. appengine.go
  11. codereview.cfg
  12. content/
  13. fmt.go
  14. go.mod
  15. go.sum
  16. gotour/
  17. local.go
  18. pic/
  19. reader/
  20. solutions/
  21. static/
  22. template/
  23. tools/
  24. tour.go
  25. tree/
  26. wc/

Go Tour

A Tour of Go is an introduction to the Go programming language. Visit to start the tour.


To install the tour from source, first install Go and then run:

$ go get

This will place a tour binary in your workspace's bin directory. The tour program can be run offline.


Contributions should follow the same procedure as for the Go project:

To run the tour server locally: app.yaml

and then visit http://localhost:8080/ in your browser.

Report Issues / Send Patches

This repository uses Gerrit for code changes. To learn how to submit changes to this repository, see

The main issue tracker for the tour is located at Prefix your issue with “tour:” in the subject line, so it is easy to find.


  1. To deploy, run:

    GO111MODULE=on gcloud --project=golang-org app deploy --no-promote app.yaml

    This will create a new version, which can be viewed within the golang-org GCP project.

  2. Check that the deployed version looks OK (click the version link in GCP).

  3. If all is well, click “Migrate Traffic” to move 100% of the traffic to the new version.

  4. You're done.


Unless otherwise noted, the go-tour source files are distributed under the BSD-style license found in the LICENSE file.