Vic Shóstak

@salinaaaaaa thanks for your reply! Please try `go mod tidy` at the root of the directory.

Could you try to run `swag init` before `make docker.run`?

@salinaaaaaa sorry, I have no idea why it's happen on your machine. Yes, I see a problem on your output: > #10 4.981 docs/docs.go:343:20: undefined: "github.com/swaggo/swag".Spec But on my side...

@mattharrigan hi! 🤝 First, check your Go version. It can be `v1.11` or higher. Next, type in console (on root of your Go project): ```console foo@bar:~/project$ go mod init github.com/user/project-name...

@mattharrigan _typically_ this files can be at root of your Go project. ```console foo@bar:~/project$ tree . . ├─ main.go

I think, better name for this project is `Golang Layout Best Practice`.

@akessner yep. Something like this: Organization: `golang-best-practices` Repos: - `project-layout` — this repo - `projects-examples` — something about _real live_ examples (separated by subject: API, CLI, etc.) - `docker-configs` —...

@cyantarek hi 🤝 I worked around this idea a few weeks (start at Nov 2019), because I need exact "lazy" solution for every new project at my current work 😉...

I think, better name for this project is `golang-best-practice`, than `golang-(non-)standard`. Because, for my self, this folder's structure is best entry point for `how to name this?` to start new...

Oh, I see. Okay, I'll try to add that, just please tell me where to look for the Electron source download call in your library?