vgo project settings need to be stored outside workspace.xml

Answered

Hi,

I've just realised that, when I set the GOPROXY settings for a project in GoLand they are stored in the workspace.xml. This won't work for me as I don't want to include workspace.xml in Git as it causes merge issues all the time. Is there a way to store this outside workspace.xml?

Thanks

Gareth

3 comments
Comment actions Permalink

Hello,

The file workspace.xml should not be included in the version control system (in the .idea folder it is by default located in .gitignore).

You can export the GOPROXY variable from your environment (.bashrc, .zshrc, and so on), and then it will be used when creating a new project (this variable can also be set using the go env -w command).

May it solve your problem? If not, could you describe the situation that you want to solve by adding GOPROXY as part of a project in Git?

I look forward to hearing from you.

0
Comment actions Permalink

Hi,

We want to ensure that the dependencies used in the project come from internal sources only, hence using a go proxy. 

We'd like our developers to have to set up as little on their machine as possible so I was hoping to include the proxy settings in the project to smooth the transition to using Go. We're also experimenting with different proxy mechanisms so it would be nice to be able to use a different proxy by setting it in the project and it being changed automatically as developers pull rather than them having to manually change it,

Cheers

Gareth

0
Comment actions Permalink

Thanks for the detailed explanation.

There is no such thing yet, but you can go to our YouTrack and leave a request for adding functionality (saving the GOPROXY variable within the project).

We will be grateful.

0

Please sign in to leave a comment.