austinfrey
austinfrey
could this be an arm specific Dockerfile in this repo?
this is probably an issue for the installer, not ssb-room: https://github.com/seven1m/do-install-button it is no longer maintained.
@ndarilek try using the `--name` flag. `ssb-server plugins.install --name ssb-about` see also: https://github.com/ssbc/ssb-server/issues/749 https://github.com/ssbc/ssb-server/issues/718
@nichoth i haven't seen one. i think the general consensus has been that a new project should be started. looking at this repo, you might be better served starting from...
@Jacobthegr8 I've had success with process managers that integrate with systemd, like `pm2` , that can autostart a service like ssb at boot time
@xe-4 the tests currently run against Node 6, 8, and 10. maybe try a PR that adds those?
Digging deeper, the error is specific to the above `hypercore` package, but since I'd added it to `package.json`the error was appearing in subsequent package installs since it looks like `dep`...
@mixmix Looking at this again, I think I was getting some wires crossed. It appeared to me that passing in a seed would not populate an id or publicKey at...
Hi @nichoth, I do not believe this is required, if it's present it gets used, if not, no big deal and it seems like it really appears mainly in tests...
@nichoth ~~correct, it can be an empty config object though I think: `App({})`~~ you might also try passing in keys `App.({keys: ssbKey.loadOrCreate()})` - edit: i think you can do `seeds`...