summaryrefslogtreecommitdiffstats
path: root/docs/content/doc/installation/from-binary.en-us.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/content/doc/installation/from-binary.en-us.md')
-rw-r--r--docs/content/doc/installation/from-binary.en-us.md11
1 files changed, 6 insertions, 5 deletions
diff --git a/docs/content/doc/installation/from-binary.en-us.md b/docs/content/doc/installation/from-binary.en-us.md
index c598317b6e..91a6b2a9d6 100644
--- a/docs/content/doc/installation/from-binary.en-us.md
+++ b/docs/content/doc/installation/from-binary.en-us.md
@@ -32,6 +32,7 @@ chmod +x gitea
```
## Verify GPG signature
+
Gitea signs all binaries with a [GPG key](https://keys.openpgp.org/search?q=teabot%40gitea.io) to prevent against unwanted modification of binaries.
To validate the binary, download the signature file which ends in `.asc` for the binary you downloaded and use the GPG command line tool.
@@ -89,11 +90,11 @@ chmod 640 /etc/gitea/app.ini
If you don't want the web installer to be able to write to the config file, it is possible to make the config file read-only for the Gitea user (owner/group `root:git`, mode `0640`) however you will need to edit your config file manually to:
- * Set `INSTALL_LOCK= true`,
- * Ensure all database configuration details are set correctly
- * Ensure that the `SECRET_KEY` and `INTERNAL_TOKEN` values are set. (You may want to use the `gitea generate secret` to generate these secret keys.)
- * Ensure that any other secret keys you need are set.
-
+* Set `INSTALL_LOCK= true`,
+* Ensure all database configuration details are set correctly
+* Ensure that the `SECRET_KEY` and `INTERNAL_TOKEN` values are set. (You may want to use the `gitea generate secret` to generate these secret keys.)
+* Ensure that any other secret keys you need are set.
+
See the [command line documentation]({{< relref "doc/usage/command-line.en-us.md" >}}) for information on using `gitea generate secret`.
### Configure Gitea's working directory