Tweaks

README.md

@@ -96,13 +96,6 @@ component. Additional UI is built using React.js.
 back-end bundles. The server backend runs as a HTTP server on node.js using
 express.
 
-After cloning the repo, run the following command to install some convenience
-scripts (`silverbullet` and `plugos-bundle` into your `~/.deno/bin`):
-
-```shell
-deno task install
-```
-
 To prepare the initial web and plug build run:
 
 ```shell

deno.jsonc

@@ -17,8 +17,7 @@
     },
     "tasks": {
       "test": "deno test -A --unstable",
-      "install": "deno install -f -A --unstable plugos/bin/plugos-bundle.ts && deno install -f -n silverbullet -A --unstable server/server.ts",
+      "build": "deno install -f -A --unstable plugos/bin/plugos-bundle.ts && ./build_plugs.sh && deno run -A --unstable --check build.ts && deno install -f -n silverbullet -A --unstable server/server.ts",
-      "build": "./build_plugs.sh && deno run -A --unstable --check build.ts",
       "watch-web": "deno run -A --unstable --check build.ts --watch",
       "watch-server": "deno run -A --unstable --check --watch server/server.ts",
       // The only reason to run a shell script is that deno task doesn't support globs yet (e.g. *.plug.yaml)

server/http_server.ts

@@ -143,11 +143,6 @@ export class HttpServer {
       "get-plug:file",
       async (plugPath: string): Promise<Manifest> => {
         const resolvedPath = path.resolve(plugPath);
-        if (!resolvedPath.startsWith(Deno.cwd())) {
-          throw new Error(
-            `Plugin path outside working directory, this is disallowed: ${resolvedPath}`,
-          );
-        }
         try {
           const manifestJson = await Deno.readTextFile(resolvedPath);
           return JSON.parse(manifestJson);