Open christianbundy opened 5 years ago
Workaround is editing ~/.ssb/config
to hardcode { name: 'foo' }
manually.
cc: @dominictarr am I doing something wrong here? For example, ssb-server plugins.install ssb-identities
sets the config as:
{
"plugins": {
"ssb-identities": {
"name": "ssb-identities"
}
}
}
which throws the above error. The fix is to manually change this to:
{
"plugins": {
"ssb-identities": {
"name": "identities"
}
}
}
Looks like this regression may have been made in https://github.com/ssbc/ssb-plugins/commit/7ee651a5fc48fe588ab24b5abe45dd013591e102, maybe we should be require()
ing the plugin to get the real plugin.name
? Or maybe we could circumvent the problem by just using true
unless it came from the filesystem.
Oh, I see, I have to specify the plugin name on the command line.
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
Currently happening with all plugins installed with
ssb-server plugins.install
.