# go-organization

Understand project structure of GO. Go Modules, GOPATH, efficent development environment... This repo contains lots of trash folder/file! Just trying to understand structure with trying lots of unnecessary things too 

### Base Resources
| Resource | Explanation | Implementation |
| -------- | ----------- | -------------- |  
| https://github.com/golang/go/wiki/Modules | - | - |
| https://go.dev/blog/using-go-modules | - | - | 
| https://github.com/golang-standards/project-layout | - | - | 
| https://go.dev/doc/code | - | - | 
| https://tutorialedge.net/golang/go-project-structure-best-practices/ | - | - | 
| https://www.digitalocean.com/community/tutorials/how-to-use-go-modules | Modules | [module-str](simple-structrue/module-str) |
| https://www.digitalocean.com/community/tutorials/how-to-write-packages-in-go | Packages | [package-str](simple-structure/package-str/) | 
| https://go.dev/ref/mod | -  | - |

### FAQ
<details>
<summary><h4>Is there any venv equal for Go language or any virtual environment tool?</h4></summary>
  <br><ul><li> No, previously GOPATH was used but now Go Modules are using instead of that. Thanks to Go Modules, go.mod file handles all versions/modules/packages and there is no need for a virtual environment. But if you have to use a virtual environment because of another reason just have a look at <a href="https://github.com/GetStream/vg">this</a> repo
  </li></ul>
</details>