You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to tweak some of the HTML on farmer.golang.org to make it more consistent with the other Go sites. It's hard to stand up the coordinator server locally.
This snippet of code suggests that it should be possible, or was at one point:
However running go install golang.org/x/build/cmd/coordinator && coordinator --mode=dev --dev_gce=false on my Macbook yields the following log:
2017/04/03 09:42:31 coordinator version "" starting
2017/04/03 09:42:31 Loaded configuration "dev" for project "":
{
"ProjectName": "",
"IsProd": false,
"Zone": "",
"ZonesToClean": null,
"StaticIP": "127.0.0.1",
"MachineType": "",
"KubeMinNodes": 0,
"KubeMaxNodes": 0,
"KubeMachineType": "",
"KubeName": "",
"KubePassword": "",
"DashURL": "",
"CoordinatorURL": "",
"CoordinatorName": "",
"BuildletBucket": "",
"LogBucket": "",
"SnapBucket": "",
"MaxBuilds": 0,
"AutoCertCacheBucket": ""
}
2017/04/03 09:42:31 Error creating datastore client: datastore: missing project/dataset id
2017/04/03 09:42:31 failed to get a token source: google: could not find default credentials. See https://developers.google.com/accounts/docs/application-default-credentials for more information.
exit status 1
Which suggests we now have a hard dependency on GCE, on this line:
tokenSource, err = google.DefaultTokenSource(ctx, compute.CloudPlatformScope)
if err != nil {
log.Fatalf("failed to get a token source: %v", err)
}
It would be good to either document what GCE settings you need to run the application locally, remove the hard dependency on GCE, or document that the coordinator can't be run outside of GCE.
The text was updated successfully, but these errors were encountered:
It's worked locally at various times, but it generally rots, as you've found. Generally we use the staging server for development & testing, since it's not easy to test something that integrates with a dozen misc APIs (all themselves changing often). Any fakes or mocks are just lies if your dependent APIs keep changing underfoot.
But changes to make it work again would be welcome.
Previously the server would fail to start if a valid token could not
be found. The local development environment still doesn't do much, but
it should let you view and edit the HTML and confirm that the server
starts, so ignore the error if we are running in dev mode.
Add a short README explaining how to start and view the coordinator
server locally.
Fixesgolang/go#19828.
Fixesgolang/go#18291.
Change-Id: I91a3ce49e1e9ea18ca19f3867edb2c71fc1b5124
Reviewed-on: https://go-review.googlesource.com/39297
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
I'd like to tweak some of the HTML on farmer.golang.org to make it more consistent with the other Go sites. It's hard to stand up the coordinator server locally.
This snippet of code suggests that it should be possible, or was at one point:
However running
go install golang.org/x/build/cmd/coordinator && coordinator --mode=dev --dev_gce=false
on my Macbook yields the following log:Which suggests we now have a hard dependency on GCE, on this line:
It would be good to either document what GCE settings you need to run the application locally, remove the hard dependency on GCE, or document that the coordinator can't be run outside of GCE.
The text was updated successfully, but these errors were encountered: