Unpacking the Google Cloud SDK and Its Relation to GOPATH
Setting up Go App Engine on macOS can be a challenging task. One of the questions that arises is where the Google Cloud SDK should be stored and what the value of GOPATH should be.
Location of Google Cloud SDK
Contrary to the original question, the Google Cloud SDK should not be placed in either $GOROOT or $GOPATH. Instead, it should be unpacked directly into your $HOME directory and the installer executed. If necessary, add it to your $PATH by appending the following line to your .bash_profile:
export PATH=$HOME/google-cloud-sdk:$PATH
Setting Up GOPATH
You should not alter your $GOPATH to include the src directory in google-cloud-sdk/platform/google_appengine/goroot/src. Doing so can lead to errors. Instead, maintain your normal $GOPATH installation. The App Engine SDK for Go automatically utilizes the sources from that directory.
Avoid Modifying GOROOT
Except when compiling a new Go version from source, you should refrain from modifying $GOROOT. It automatically sets the appropriate $GOROOT value. If you encounter a corrupted installation, remove the cloud SDK, clean up any path references, and perform a fresh installation of both Go and the Google Cloud SDK.
Development Process
When developing for App Engine, your Go sources reside in your regular $GOPATH. Do not place them in the google-cloud-sdk folder. To execute dev_appserver locally, navigate to your project path and run:
dev_appserver.py [path-to-source]
where [path-to-source] contains your code and app.yaml.
Folder Structure
For clarity, here is a simplified representation of the recommended folder structure:
$GOPATH = $HOME/go ├── src │ ├── myproject │ │ └── main.go │ │ └── app.yaml
Google Cloud SDK:
$HOME/google-cloud-sdk ├── bin ├── ... ├── platform │ └── google_appengine │ └── ...
The above is the detailed content of Where Should I Install the Google Cloud SDK and Set GOPATH for Go App Engine Development?. For more information, please follow other related articles on the PHP Chinese website!