#Forking of gocloud.dev
6 messages · Page 1 of 1 (latest)
Also I have come across an issue in go-cloud repo:
I will point out that nothing prevents you from developing a separate provider out-of-tree. This has been done by folks before, and it works well.
Does anyone know what this means? Thanks
To my knowledge you'd just fork it then change the imports from "github.com/theirlibrary" to "github.com/yourlibrary"
then run a go mod tidy ?
Or you can clone it and put it in your "src" ( typically in ~/go/src or users folder in windows ) then go from there
Thanks for the reply, appreciate it.
In the source of the project I'm working on.
"github.com/inngest/inngest/pkg/config"
"github.com/inngest/inngest/pkg/inngest/log"
"github.com/inngest/inngest/pkg/logger"
"gocloud.dev/pubsub"
_ "gocloud.dev/pubsub/awssnssqs"
_ "gocloud.dev/pubsub/gcppubsub"
_ "gocloud.dev/pubsub/mempubsub"
_ "gocloud.dev/pubsub/natspubsub"
"golang.org/x/sync/semaphore"
I'm now hoping to just suppliment with my own version
And that means it will be picked up? But I'm not sure if I am missing anything fundamental just yet.
I'm still at the stage of converting an existing implementation to work with pulsar