Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
export GOPATH=“$HOME/projects/src” should be export GOPATH=“$HOME/projects” preferably it should be GOPATH=“$HOME/goworkspace” but that’s to the user’s preference
If you’re running into a problem where you follow the above steps, sans the parts involving editing and configuring a ~/.bash_profile file – opting instead only to edit your /etc/profile.d/path.sh (/etc/profile) file, then read here!
Assuming you succeeded in following all other steps successfulling, and you’ve reloaded your profile, you may find that the results of “which go” will indicate that no Golang installation is being detected. Just add the line, “source /etc/profile”, to your ~/.bash_profile. I preferred to do this, since it minimilized my Golang workflow’s dependency on the highly volatile, user-specific ~/.bash_profile file – at least down to only one line.
For some reason (at least with me, in my CentOS context), go was only finally recognized after login, and only once I explicitly commanded “source /etc/profile”.
Hi i am getting the following error /bin/bash: go: command not found make: *** [all] Error 127
go is working file with me…