Join Us In Slack: https://gophers.slack.com | #go-plus | https://gophersinvite.herokuapp.com to get access
https://run.pivotal.io (disclosure: my employer)
All of them
All of them run your app in a container
And externalize the datastore
sounds like it's one of those decisions that has pros/cons on either side... just feels weird to change course so drastically to get gocode working, hehe
/ security model
Which is ultimately why you have to have a separate runtime
The app engine approach is not the future of GCE, so I wouldn't start there for new apps
Ah!! cool I found the solution for gocode - setting lib-path: gocode set lib-path C:\Users\david\Documents\GOPATH\pkg\windows_amd64_appengine
:D
(and auto-build off since gocode doesn't use goapp... not sure whether or not it's a race condition against your builder-go, but anyway to get around that I guess I could periodically run goapp install or trigger builds then try again or whatever)
What shell do you use?
export GOPATH=/Users/yourusername/go
In .profile or .bash_profile or .zshrc
also, make sure $GOPATH/bin is in your path
@alexmozzhakov
quit atom and relaunch if you have already done this
@alexmozzhakov that is a shell initialization script
run every time you launch a new terminal
Hello. Iam having a problem with missing errors when saving. But when I build the go application manually in the terminal it returns a bunch of errors. Back in the days go-plus also showed all build errors this when saving the application in Atom. How should I fix this? There is one console error in Atom: "[Package-Deps] Unable to get package info for json-lint-provider" Maybe this is related?
I am running Atom version 1.8 by the way. Thanks for any help.
You have a few options: 1) set it as a user environment variable and log out / log in 2) system environment variable and reboot or 3) set the config in go-config package settings for GOPATH
@ErthyLoL_twitter
'C:\Users\roese>go env
set GOARCH=amd64
set GOBIN=
set GOEXE=.exe
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOOS=windows
set GOPATH=C:\BTSync\Developing\Go
set GORACE=
set GOROOT=C:\Go
set GOTOOLDIR=C:\Go\pkg\tool\windows_amd64
set GO15VENDOREXPERIMENT=1
set CC=gcc
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0
set CXX=g++
set CGO_ENABLED=1'
set GOARCH=amd64
set GOBIN=
set GOEXE=.exe
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOOS=windows
set GOPATH=C:\BTSync\Developing\Go
set GORACE=
set GOROOT=C:\Go
set GOTOOLDIR=C:\Go\pkg\tool\windows_amd64
set GO15VENDOREXPERIMENT=1
set CC=gcc
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0
set CXX=g++
set CGO_ENABLED=1'
I think my GOPATH is set, the only question is if correctly.
(Sorry for not quite understanding everything and for such a prompt response @joefitzgerald !)
That looks good, right?