Rename LFS_JWT_SECRET to include OAUTH2 as well (#6826)

This commit is contained in:
techknowlogick 2019-05-01 22:32:06 -04:00 committed by GitHub
parent e255df83a6
commit 897927690f
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 6 additions and 5 deletions

View file

@ -40,8 +40,9 @@ var (
} }
microcmdGenerateLfsJwtSecret = cli.Command{ microcmdGenerateLfsJwtSecret = cli.Command{
Name: "LFS_JWT_SECRET", Name: "JWT_SECRET",
Usage: "Generate a new LFS_JWT_SECRET", Aliases: []string{"LFS_JWT_SECRET"},
Usage: "Generate a new JWT_SECRET",
Action: runGenerateLfsJwtSecret, Action: runGenerateLfsJwtSecret,
} }

View file

@ -161,11 +161,11 @@ for automatic deployments.
- `secret`: - `secret`:
- Options: - Options:
- `INTERNAL_TOKEN`: Token used for an internal API call authentication. - `INTERNAL_TOKEN`: Token used for an internal API call authentication.
- `LFS_JWT_SECRET`: LFS authentication secret. - `JWT_SECRET`: LFS & OAUTH2 JWT authentication secret (LFS_JWT_SECRET is aliased to this option for backwards compatibility).
- `SECRET_KEY`: Global secret key. - `SECRET_KEY`: Global secret key.
- Examples: - Examples:
- `gitea generate secret INTERNAL_TOKEN` - `gitea generate secret INTERNAL_TOKEN`
- `gitea generate secret LFS_JWT_SECRET` - `gitea generate secret JWT_SECRET`
- `gitea generate secret SECRET_KEY` - `gitea generate secret SECRET_KEY`
#### keys #### keys