diff options
author | cel <cel@lOUVT+Phkvai9a/cCS/RKo+S9hnPAQdVixms/7ldpPA=.ed25519> | 2020-07-09 20:23:42 -0400 |
---|---|---|
committer | cel <cel@lOUVT+Phkvai9a/cCS/RKo+S9hnPAQdVixms/7ldpPA=.ed25519> | 2020-07-09 20:45:51 -0400 |
commit | 031b70f8c5d4ca4d8e54efea63f13a58509d4d48 (patch) | |
tree | 9d884a147682f44df0aa2253b36dbc9a9b78e0a5 | |
parent | a4d79eca377e0e9e8bda8b137d30bfdf40c852d1 (diff) | |
download | patchfoo-031b70f8c5d4ca4d8e54efea63f13a58509d4d48.tar.gz patchfoo-031b70f8c5d4ca4d8e54efea63f13a58509d4d48.zip |
%HWJLkLhiapPIaWn2yBOsFIeLNwyrYdSn/Z8cDqiBBi4=.sha256
ssb-client is now included, even if --production is used for install
-rw-r--r-- | README.md | 14 | ||||
-rw-r--r-- | doc/install-guide.html | 7 |
2 files changed, 6 insertions, 15 deletions
@@ -82,9 +82,7 @@ Running as a standalone process this way is useful if you can use git-ssb and ss ```sh git clone ssb://%YAg1hicat+2GELjE2QJzDwlAWcx0ML+1sXEdsWwvdt8=.sha256 patchfoo cd patchfoo -ssb-npm install \ - --branch %e/unnFWjNwhJuFtH+DmkNqqvVggrufu/sZxRU5e59Is=.sha256 \ - --branch %FlwIBeDR/liKcEvok7uF9o3e7Qib36aMj1orj3aiFVQ=.sha256 +ssb-npm install --production --branch %HWJLkLhiapPIaWn2yBOsFIeLNwyrYdSn/Z8cDqiBBi4=.sha256 npm start ``` @@ -92,13 +90,11 @@ npm start This is the traditional way to install and run patchfoo. -Using `--production` skips installing `ssb-client`, which is not needed for plugin usage. If you want to also be able to run patchfoo as a standalone process, omit the `--production` option in the commands below, and add the extra `--branch` parameter as used above. - ```sh cd ~/.ssb/node_modules git clone ssb://%YAg1hicat+2GELjE2QJzDwlAWcx0ML+1sXEdsWwvdt8=.sha256 patchfoo cd patchfoo -ssb-npm install --production --branch %e/unnFWjNwhJuFtH+DmkNqqvVggrufu/sZxRU5e59Is=.sha256 +ssb-npm install --production --branch %HWJLkLhiapPIaWn2yBOsFIeLNwyrYdSn/Z8cDqiBBi4=.sha256 node enable-plugin.js ``` @@ -122,9 +118,7 @@ This installs patchfoo globally and gives you a `patchfoo` executable. Note: if you previously installed a patchfoo binary release, [ssb-]npm will not overwrite it. You must manually remove it (e.g. `rm ~/.local/bin/patchfoo`) before installing via ssb-npm. ```sh -ssb-npm install -g patchfoo \ - --branch %e/unnFWjNwhJuFtH+DmkNqqvVggrufu/sZxRU5e59Is=.sha256 \ - --branch %FlwIBeDR/liKcEvok7uF9o3e7Qib36aMj1orj3aiFVQ=.sha256 +ssb-npm install -g patchfoo --branch %HWJLkLhiapPIaWn2yBOsFIeLNwyrYdSn/Z8cDqiBBi4=.sha256 ``` ### as a ssb-server plugin @@ -132,7 +126,7 @@ ssb-npm install -g patchfoo \ This does a global ssb-npm install and then symlinks it into place and installs it with ssb-server as a plugin. ```sh -ssb-npm install -g patchfoo --branch %e/unnFWjNwhJuFtH+DmkNqqvVggrufu/sZxRU5e59Is=.sha256 +ssb-npm install -g patchfoo --branch %HWJLkLhiapPIaWn2yBOsFIeLNwyrYdSn/Z8cDqiBBi4=.sha256 dir=$(dirname $(realpath $(which patchfoo))) ln -s "$dir" ~/.ssb/node_modules/ node "$dir/enable-plugin.js" diff --git a/doc/install-guide.html b/doc/install-guide.html index 04a07cf..e1d6a8f 100644 --- a/doc/install-guide.html +++ b/doc/install-guide.html @@ -42,9 +42,7 @@ ssb-npm install -g git-ssb@2.8.0 \ <pre> git clone ssb://%YAg1hicat+2GELjE2QJzDwlAWcx0ML+1sXEdsWwvdt8=.sha256 patchfoo cd patchfoo -ssb-npm install \ - --branch %e/unnFWjNwhJuFtH+DmkNqqvVggrufu/sZxRU5e59Is=.sha256 \ - --branch %FlwIBeDR/liKcEvok7uF9o3e7Qib36aMj1orj3aiFVQ=.sha256 +ssb-npm install --production --branch %HWJLkLhiapPIaWn2yBOsFIeLNwyrYdSn/Z8cDqiBBi4=.sha256 npm start </pre> @@ -54,8 +52,7 @@ mkdir ~/.ssb/node_modules cd ~/.ssb/node_modules git clone ssb://%YAg1hicat+2GELjE2QJzDwlAWcx0ML+1sXEdsWwvdt8=.sha256 patchfoo cd patchfoo -ssb-npm install --production \ - --branch %e/unnFWjNwhJuFtH+DmkNqqvVggrufu/sZxRU5e59Is=.sha256 +ssb-npm install --production --branch %HWJLkLhiapPIaWn2yBOsFIeLNwyrYdSn/Z8cDqiBBi4=.sha256 node enable-plugin.js </pre> <p>Restart ssb-server or Patchwork.</p> |