How to start a Go project in 2018

Re:How to start a Go project in 2018 by imjasonmiller on Monday May 14, 2018 @04:04AM (#17063690)

If I may ask, how do you handle the use of other languages within a project that uses Go? I am new to Go, so it might be a silly question.

I currently have a project that uses Node and React for the front-end and Go for streaming and scraping large .xml + .json data due to its great standard library.

With Node I can start a project wherever I would like — e.g. D:/work/node_project. Go seems to be much more opinionated on that? I opted to follow Go’s preferred directory structure and include npm related packages there, but feel I am not following best practices. Ideally, I would like to have one directory for my projects.

I will take a good look at vgo this afternoon. It removing the need for GOPATH sounds interesting. Thank you.

[ Parent | on HN ]

Re:How to start a Go project in 2018 by nzoschke on Monday May 14, 2018 @09:43AM (#17065416)

I make the go server/package the repo and add a web/ subdirectory for my static and dynamic JavaScript code, plus a little bit of Makefile glue.

Here is a boilerplate Go Lambda app with a Node Lambda function and a static Vue app:

https://github.com/nzoschke/gofaas

[ Parent | on HN ]