Restructure the code and take out logic to a separate service level about dunner HOT 4 CLOSED

I think we can create an interface which is a collection of services and we can call these methods/services from do.go

from dunner.

here I have implemented the interfaces in Python to make it easy for us to work with. please refer the branch 'python-function-protos'

from dunner.

The current structure in approved in #12 is not quite according to the Golang standard accepted by the community. Have a look at this repo and this section of "Effective Go". Although it is not an official structure, but it has been developed by observing the trend in bigger projects in Golang.
A small possible restructure patch could be (including the test files as mentioned in my comment on #13 ),

.
+-- cmd/
|    +-- do/
|    |    +-- do.go
|    |    +-- do_test.go
.    .
.    


+-- pkg/
|    +-- services/
|    |    +-- config/
|    |    |    +-- config.go
|    |    |    +-- config_test.go
|    |    +-- docker/
|    |    |    +-- docker.go
|    |    |    +-- docker_test.go
.    .    .
.    .
.

I will be ready a PR soon enough if someone approves the suggestion. Also, can this issue be re-opened?

from dunner.

@ayushjn20 I reopened the issue, you can send a PR

from dunner.