According to Rob Pike, there can't be a single way to lay out a Go project. Different project types have different needs, so a good layout should follow common sense and good practices.
This article explains how to structure a Go project, from command-line tools to large application projects, while keeping import paths short and consistent. It also highlights the benefits of using dedicated directories for packages and keeps the layout simple to avoid confusion.
Share with your friends and followers
Start blogging about your favorite technologies, reach more readers and earn rewards!
Join other developers and claim your FAUN account now!
Only registered users can post comments. Please, login or signup.