summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorYannick Bungers2021-05-08 16:07:10 +0200
committerGitHub2021-05-08 16:07:10 +0200
commitdb50bdf91934ff063d075a4be29553c018a1b5af (patch)
tree233592548bb4dc49149c53cca7942a8bb5a4a0f5 /docs
parent3e836d815baf3f98fb6b263b5aa123d81f78fb9c (diff)
parenta4b4ebd80c2c94d7e14eee18a9928f63d653efc9 (diff)
Merge pull request #1249 from hedgedoc/adjustSetup
Docs: Add mention to install devDependencies
Diffstat (limited to 'docs')
-rw-r--r--docs/content/setup/manual-setup.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/content/setup/manual-setup.md b/docs/content/setup/manual-setup.md
index bbd73f79..f3ce3702 100644
--- a/docs/content/setup/manual-setup.md
+++ b/docs/content/setup/manual-setup.md
@@ -34,7 +34,7 @@
It's also possible to use environment variables.
For details, have a look at [the configuration documentation](../configuration.md).
5. *:octicons-light-bulb-16: If you use the release tarball for 1.7.0 or newer, this step can be skipped.*
- Build the frontend bundle by running `yarn run build`.
+ Build the frontend bundle by running `yarn install` and then `yarn build`. The extra `yarn install` is necessary as `bin/setup` does not install the build dependencies.
6. It is recommended to start your server manually once:
```shell
NODE_ENV=production yarn start
@@ -61,7 +61,7 @@ If you want to upgrade HedgeDoc from an older version, follow these steps:
<small>If you use Git, you can check out the new tag with e.g. `git fetch origin && git checkout 1.8.1`</small>
5. Run `bin/setup`. This will take care of installing dependencies. It is safe to run on an existing installation.
6. *:octicons-light-bulb-16: If you used the release tarball for 1.7.0 or newer, this step can be skipped.*
- Build the frontend bundle by running `yarn run build`.
+ Build the frontend bundle by running `yarn install` and `yarn build`. The extra `yarn install` is necessary as `bin/setup` does not install the build dependencies.
7. It is recommended to start your server manually once:
```shell
NODE_ENV=production yarn start