Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
This mother of all things has a dedicated src directory, so it really comes down to each project to choose its own file structure.
I think it would be so much nicer to have an import path like: github.com/group/project
Why src directory? Git repos are for source code, such name is meaningless. For complex projects I prefer using standard go project layout. For single package or single command projects flat repo is OK.
NOTE:
The number of mentions on this list indicates mentions on common posts plus user suggested alternatives.
Hence, a higher number means a more popular project.
Related posts
- I'm coming from Java and I have been told that I'm writing go like I'm writing Java. Basically creating structs, injecting fields, and attaching methods. What else can I do?
- Why does my import have a custom name?
- How to write Go
- Do I understand this correct? Project structure & design in GO
- Clean architecture/ best practices in Go?