README
¶
Cloud Foundry Go(Lang) Buildpack
A Cloud Foundry buildpack for Go(lang) based apps.
This is based on the [Heroku buildpack] (https://github.com/heroku/heroku-buildpack-go).
Using the Buildpack
For information on deploying Go applications visit CloudFoundry.org.
Building the Buildpack
- Make sure you have fetched submodules
git submodule update --init
- Get latest buildpack dependencies
BUNDLE_GEMFILE=cf.Gemfile bundle
- Build the buildpack
BUNDLE_GEMFILE=cf.Gemfile bundle exec buildpack-packager [ --uncached | --cached ]
- Use in Cloud Foundry
Upload the buildpack to your Cloud Foundry and optionally specify it by name
cf create-buildpack custom_go_buildpack go_buildpack-cached-custom.zip 1
cf push my_app -b custom_go_buildpack
Testing
Buildpacks use the Machete framework for running integration tests.
To test a buildpack, run the following command from the buildpack's directory:
BUNDLE_GEMFILE=cf.Gemfile bundle exec buildpack-build
More options can be found on Machete's Github page.
Contributing
Find our guidelines here.
Help and Support
Join the #buildpacks channel in our [Slack community] (http://slack.cloudfoundry.org/) if you need any further assistance.
Reporting Issues
Please fill out the issue template fully if you'd like to start an issue for the buildpack.
Active Development
The project backlog is on Pivotal Tracker
Directories
¶
| Path | Synopsis |
|---|---|
|
cf_spec
|
|
|
fixtures/go99/src/go99
command
|
|
|
fixtures/go_16_app/src/go_app
command
|
|
|
fixtures/go_app/src/go_app
command
|
|
|
fixtures
|
|
|
util/proxy
module
|
|
|
test
|
|
|
fixtures/godep-basic
command
|
|
|
fixtures/godep-bin-file
command
|
|
|
fixtures/godep-cgo-basic
command
|
|
|
fixtures/godep-devel-go
command
|
|
|
fixtures/godep-ld-symbol-value
command
|
|
|
fixtures/godep-massage-vendor
command
|
|
|
fixtures/godep-old-workspace
command
|
|
|
fixtures/godep-old-workspace/Godeps/_workspace/src/github.com/heroku/slog
Package slog provides some Structred Logging helpers ATM: Mostly used to hold some context for a http handler and log at the end of a request Generally should provide the oposite of logfmt: https://github.com/kr/logfmt Sample use in a http.HandleFunc http.HandleFunc("/health", func(w http.ResponseWriter, r *http.Request) { start := time.Now() ctx := slog.Context{} defer func() { fmt.Println(ctx) }() defer func() { ctx.Measure("health.check.duration", time.Since(start)) }() ctx.Count("health.check",1) ...stuff }) Produces a line like so for every request: count#health.check=1 measure#health.check.duration=0.004s
|
Package slog provides some Structred Logging helpers ATM: Mostly used to hold some context for a http handler and log at the end of a request Generally should provide the oposite of logfmt: https://github.com/kr/logfmt Sample use in a http.HandleFunc http.HandleFunc("/health", func(w http.ResponseWriter, r *http.Request) { start := time.Now() ctx := slog.Context{} defer func() { fmt.Println(ctx) }() defer func() { ctx.Measure("health.check.duration", time.Since(start)) }() ctx.Count("health.check",1) ...stuff }) Produces a line like so for every request: count#health.check=1 measure#health.check.duration=0.004s |
|
fixtures/godep-vendor
command
|
|
|
fixtures/govendor-basic
command
|
|