Patchbay installers

here's a thread where I'll post up experimental patchbay builds which use scuttle-shell

Llinux installer

TRY IT HERE : https://github.com/ssbc/patchbay/releases/tag/v7.15.6-scuttle-shell-alpha

built using https://github.com/ssbc/patchbay-builder/pull/1

• builds
• appImage runs!
• appImage runs on a fresh linux install
  • needs testing

This is great news! So I can develop my client and can in paralel run a working client and check stuff back.

@mix I installed using the appimage this morning and it seemed to come up fine. I'm not usually running patchbay so I don't have a lot of context on general speed etc but I can definitely see the scuttleshell in my tray when I start patchbay and it closes when I close patchbay

hey @Tim Schumacher (work) / @Tim Schumacher it will depend how your initial scuttle-shell is being started - with what config... the current way I'm detecting a scuttle-shell running is to see if ssb-client can connect to an sbot ... but it does this assuming certain config

https://github.com/ssbc/patchbay/pull/295/files#diff-78c12f5adc1848d13b1c6f07055d996eR13

Note the scuttle-shell I'm running in here is the branch refactor_config which, in which I've modified the config that scuttle-shell is starting with (because patchbay couldn't connect otherwise, and I'm still learning how this connections config works):

https://github.com/ssbc/scuttle-shell/pull/24/files#diff-e22b50e740e102c8de5e858dbcd7753dR15

Would love to hear about your setup and see if you have an ok time if you're running that branch.

@DavidW thanks for testing this. Out of interest do you do development on linux (this matters because if you are building stuff you probably have some .so files in place which a fresh install might not)

@mixmix - woah, this is awesome =D.

I had to remove my ~/.ssb/config file (which had a bunch of <plugin name>: true lines in it. I dunno how this file got here and if other people would run into this situation, or if it's some artifact of me faffing around with dev stuff?

I lost the errors on my clipboard, but it was something like "ssb-about has already been loaded", "chess-db has already been loaded", etc, and it prevented everything from starting up. I can try and reproduce it by crafting a ~/.ssb/config file if you like? I don't seem to have one now, so I dunno how I got one in the first place...

I forgot that binary versions of patchbay run much quicker than my source version i normally use (i think probably because i'm not on the version of node that compiles sodium using C or something - i seen that mentioned in a thread recently...) so that's a nice side effect too.

Anyway, excited for a day where I'm running a bunch of independent apps off the same scuttle-shell =D

@happy0 that config file is something you put there ! Yeah it is a good gotcha to know about .. scuttle-shell checks a range of places for custom plugins to run, this is one of them

nah don't worry about reproducing, this would be a known bug.

Yeah I had wondered if it was a bit quicker ... but always hard to know if it's just your imagination.

I do development on my machine, yes. Not much node related, but you're right that I have a good number of dev packages installeed

Hello @mix

hey @Tim Schumacher (work) / @Tim Schumacher it will depend how your initial scuttle-shell is being started - with what config... the current way I'm detecting a scuttle-shell running is to see if ssb-client can connect to an sbot ... but it does this assuming certain config

It was a plain master instance with one little patch:

diff --git a/server.js b/server.js
index dbb5081..27512ff 100755
--- a/server.js
+++ b/server.js
@@ -27,7 +27,7 @@ function start (customConfig, donecb) {
   let ssbAppName = appname || process.env.ssb_appname

   const config = require('ssb-config/inject')(ssbAppName, minimist(conf))
-
+  config.connections.incoming.net[0].host = '127.0.0.1'
   const keys = ssbKeys.loadOrCreateSync(path.join(config.path, 'secret'))
   if (keys.curve === 'k256') {
     // i think this is _really_ old and could be removed

I needed this because somehow the ssb server listened on my public ip address and other clients could not connect to the server.

Starting patchbay without the external scuttle shell did work and started scuttle-shell juuust fine