mirror of
https://codeberg.org/forgejo/docs.git
synced 2025-01-22 02:15:25 -05:00
Add a note about keychain storage location quirks
Signed-off-by: Octol1ttle <l1ttleofficial@outlook.com>
This commit is contained in:
parent
18938804e6
commit
5f017fbf77
1 changed files with 9 additions and 0 deletions
|
@ -62,6 +62,15 @@ The `default` option will interrogate `git config` for
|
|||
`commit.gpgsign` option - if this is set, then it will use the results
|
||||
of the `user.signingkey`, `user.name` and `user.email`.
|
||||
|
||||
By default, Forgejo will look for the signing key in `[git].HOME_PATH/.gnupg`.
|
||||
|
||||
However, this path differs from where GnuPG stores keys by default (`$HOME/.gnupg`).
|
||||
|
||||
There are 2 possible solutions here:
|
||||
|
||||
1. Move the `.gnupg` folder after importing/generating keys;
|
||||
2. Set the `GNUPGHOME` environment variable to help Forgejo find the correct keychain.
|
||||
|
||||
### `INITIAL_COMMIT`
|
||||
|
||||
This option determines whether Forgejo should sign the initial commit
|
||||
|
|
Loading…
Add table
Reference in a new issue