I've published a new version of the gopassbridge plugin for firefox and chrome. I would consider the combination of plugin and gopass as beta. So it should work for most users/ cases. I just wonder where to place the documentation how to set up gopass with the corresponding browser plugin?
User visits the github repo
-> setup.md is already linked
User has gopass installed
when gopass jsonapi [-help] is called, also print out a link to the documentation, e.g. section in setup.md
What are your thoughts about this?
I would also prefer to install the wrapper script outside of $PATH, since the wrapper prevents the first tabbing for autocompletion. How about placing the wrapper alongside with the configuration or manifest? In both cases, it would guarantee that the target directory is writeable for the user, e.g. if your're performing a non-global installation.
I've published a new version of the gopassbridge plugin for firefox and chrome. I would consider the combination of plugin and gopass as beta. So it should work for most users/ cases. I just wonder where to place the documentation how to set up gopass with the corresponding browser plugin?
candidates are: a section in docs/setup.md
a separate file, e.g. docs/browser.md, linked from setup.md
Possible entrypoints for the user are
gopass jsonapi [-help]
is called, also print out a link to the documentation, e.g. section in setup.mdWhat are your thoughts about this?
I would also prefer to install the wrapper script outside of
$PATH
, since the wrapper prevents the first tabbing for autocompletion. How about placing the wrapper alongside with the configuration or manifest? In both cases, it would guarantee that the target directory is writeable for the user, e.g. if your're performing a non-global installation.