Open LF-DevJourney opened 4 weeks ago
Normally, there will be. Is it convenient to show the current directory structure, IDL and generation commands?
Here is the directory tree.
$ tree
.
|-- biz
| |-- dal
| | |-- init.go
| | |-- mysql
| | | `-- init.go
| | `-- redis
| | `-- init.go
| |-- handler
| | `-- hello
| | `-- example
| | |-- hello_service.go
| | `-- hello_service_test.go
| |-- router
| | |-- hello
| | | `-- example
| | | |-- hello.go
| | | `-- middleware.go
| | `-- register.go
| |-- service
| | `-- hello_method.go
| `-- utils
| `-- resp.go
|-- conf
| |-- conf.go
| |-- dev
| | `-- conf.yaml
| |-- online
| | `-- conf.yaml
| `-- test
| `-- conf.yaml
|-- docker-compose.yaml
|-- go.mod
|-- go.sum
|-- hertz_gen
| `-- hello
| `-- example
| `-- hello.go
|-- idl
| `-- hello.thrift
|-- main.go
|-- null
|-- readme.md
`-- script
`-- bootstrap.sh
21 directories, 23 files
I use the windows 11 gitbash console
Windows does not generate the build.sh file.
The documentation is not specific enough, and following it in practice can lead to many issues, which is a significant challenge for beginners.
I've experience so many issues and some dead links when learn the cloudwego.
I think improve the doc quality and keep updating is very important for the beginners.
Thanks for your advice, you are welcome to contribute when you find some bugs. Always welcome~
I follow by this page:https://www.cloudwego.io/docs/cwgo/getting-started/
but the step 5 there is no build.sh file.
go mod tidy && go mod verify sh build.sh && sh output/bootstrap.sh