Hi everyone,
Up until now I've been structuring my project by containing a services'
proto files in the same folder as the service itself, as below:
- serviceOne
- serviceOne.py
- protos
- serviceOne.proto
- serviceOne_pb2.py
- serviceOne_pb2_grpc.py
- serviceOne.pb.go
- serviceOne_grpc.pb.go
This would be for a server written in Python, being called by a client
written in Go. This has been working perfectly fine but I'm trying some
different project structures to try and get around the client needing all
of the server's generated code in order to get the proto files.
I'm trying out the following file structure as a possible alternative:
- protos
- serviceOneProto
- v1
- serviceOne.proto
- python
- serviceOne_pb2.py
- serviceOne_pb2_grpc.py
- go
- serviceOne.pb.go
- serviceOne_grpc.pb.go
- services
- serviceOne
- serviceOne.py
-serviceTwo
-serviceTwo.go
Here, the proto files are all contained within their own directory, with
the generated proto files being stored in language-specific folders.
I just wanted to find out if there are any glaring reasons against
following a project structure like this and, if not, what would be the best
way to importing the proto files (should one create a module for each
service's proto files)? I've been fighting around with some ModuleNotFound
errors trying to get the Python service to run with this structure - so any
assistance would be greatly appreciated!
--
You received this message because you are subscribed to the Google Groups
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/grpc-io/62237bcd-5899-40e6-addf-771dddf14cedn%40googlegroups.com.
