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.
Do you mean where to put the directory, or the demo CLI pattern? I loosely base my directory structure on https://github.com/golang-standards/project-layout (I should probably put it into the examples directory). Otherwise, it seems like the overall guiding principal for the CLI tool is the Unix philosophy. Admittedly, binary output probably falls outside strict guidelines but I've taken some liberties.
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
- Nunu: A CLI tool for building Go applications
- What's your go to literature to build Go libraries?
- 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?
- Can I point a module to a subdirectory?
- How To Build A Containerized Microservice in Golang: A Step-by-step Guide with Example Use-Case