Golgi could vendor go-sbot? #59
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: golgi-ssb/golgi#59
Reference in New Issue
Block a user
Possibly interesting! Upstream binaries are on the way, you can already test with:
So,
golgicould even just vendor this binary to somewhere internally managed and users of the library wouldn't even have to set one up themselves.You can pass custom repo path for
go-sbotitself and then pass custom unixsock / key forsbotcli, so it should work.Huh...that's an interesting idea. How would the deployment / installation of
go-sbotwork? Include a script(s) ingolgito do that?This reminds me that I really need to tackle: #57
Will probably do that after
tangles.threadswork is complete.Nice yeh, I guess you could just curl/download the binary via a URL which picks the right architecture and fires it up with a shell command.
Sounds a bit involved but also I like how Patchwork just vendors away the ssb-server so you don't have to think about it. So, it feels like a good approach. I'm thinking it might make golgi feel more "native" in that, you don't have to know about go-sbot/sbotcli, the library downloads & interacts with them. Then you're just rusting away as you like.
I'm experimenting with Go scripts which manage the go-sbot instance internally and it makes it nicer to manage imho. Just a drive-by thought anyway, close away if not a focus, all good!
Cool, that sounds like a nice solution to me!
Totally. I know @notplants was really keen to lower the barriers for client developers using
golgiand this feels like a neat way to do it. I'm going to leave this issue open for now because I think it'll be a great improvement to developer experience without too much effort required to implement.