* Add missing word
* Rename `boolPtr` to `forkPtr`
This is in order to be consistent with the other flags `wordPtr` &
`numbPtr` which are based on the name of the flag and not the type of
the flag.
The new Go-based code works fine and has successfully uploaded the site
several times now. This removes a dependency on a non-Go flow which
should make development easier.
The script sets up the -region and -bucket flags to point to the right S3
location. AWS_* env vars should still be set manually.
The old Ruby uploading code is moved to upload-ruby-old for now (will be
deleted later)
* Clarify comment for the goroutines sample.
The current comment may be interpreted to say that the output must be
interleaved, when in fact it doesn't have to be (it depends on the order
the goroutines are run). Make the comment more permissive to avoid the
confusion.
Fixes#365
* Fix phrasing in comment
Now that we have a go.mod, we can properly upgrade to blackfriday/v2
The output remains the same, but this PR brings back italic links with '_',
placing them into the link since this seems to be the more proper way.
Fixes#182
This isn't strictly necessary to work with the
examples from this tutorial, but knowing the
latest behavior of the go toolchain will be helpful
when users start to extend the examples.
After go1.16, go will use module mode by default,
even when the repository is checked out under GOPATH
or in a one-off directory. Add go.mod, go.sum to keep
this repo buildable without opting out of the module
mode.
> go mod init github.com/mmcgrana/gobyexample
> go mod tidy
> go mod vendor
In module mode, the 'vendor' directory is special
and its contents will be actively maintained by the
go command. pygments aren't the dependency the go will
know about, so it will delete the contents from vendor
directory. Move it to `third_party` directory now.
And, vendor the blackfriday package.
Note: the tutorial contents are not affected by the
change in go1.16 because all the examples in this
tutorial ask users to run the go command with the
explicit list of files to be compiled (e.g.
`go run hello-world.go` or `go build command-line-arguments.go`).
When the source list is provided, the go command does
not have to compute the build list and whether it's
running in GOPATH mode or module mode becomes irrelevant.
