Lines 7-21
Link Here
|
7 |
# |
7 |
# |
8 |
# This sample configuration runs Gitea with a local database. Before |
8 |
# This sample configuration runs Gitea with a local database. Before |
9 |
# running this configuration, make sure to change the INTERNAL_TOKEN, |
9 |
# running this configuration, make sure to change the INTERNAL_TOKEN, |
10 |
# JWT_SECRET, and SECRET_KEY variables. SECRET_KEY is a password of your |
10 |
# JWT_SECRET, LFS_JWT_SECRET, and SECRET_KEY variables. SECRET_KEY is |
11 |
# choosing, INTERNAL_TOKEN is a 64-byte random number in BASE64 encoding, |
11 |
# a password of your choosing, INTERNAL_TOKEN is a 64-byte random |
12 |
# JWT_SECRET is a 32-byte random number in BASE64 encoding. |
12 |
# number in BASE64 encoding, JWT_SECRET is a 32-byte random number in |
|
|
13 |
# BASE64 encoding. |
13 |
# |
14 |
# |
14 |
# You can generate the token using for example: |
15 |
# You can generate appropriate values using: |
15 |
# openssl rand -base64 64 |
16 |
# gitea generate secret [INTERNAL_TOKEN|JWT_SECRET|LFS_JWT_SECRET|SECRET_KEY] |
|
|
17 |
# and then copy that output to the appropriate place in this file. |
16 |
# |
18 |
# |
17 |
# You can let Gitea add these to the config for you; you need to make |
19 |
# Alternatively, you can let Gitea add these to the config for you; you |
18 |
# app.ini writeable by the git user. |
20 |
# need to make app.ini writeable by the git user. |
19 |
# |
21 |
# |
20 |
# There are no pre-configured users; the first user to register becomes an |
22 |
# There are no pre-configured users; the first user to register becomes an |
21 |
# admin. In this sample configuration, the HTTP server only listens on |
23 |
# admin. In this sample configuration, the HTTP server only listens on |