Skip to content

Commit eec1dbd

Browse files
committed
no need to regenerate secret key on clean slate
Signed-off-by: Phill Kelley <[email protected]>
1 parent cd3ca65 commit eec1dbd

File tree

1 file changed

+1
-15
lines changed

1 file changed

+1
-15
lines changed

docs/Containers/Gitea.md

Lines changed: 1 addition & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -224,21 +224,7 @@ Proceed as follows:
224224
$ cd ~/IOTstack
225225
$ docker compose down gitea gitea_db
226226
$ sudo rm -rf ./volumes/gitea
227-
$ docker compose up -d
228-
```
229-
230-
In this situation, you should also regenerate the secret key:
231-
232-
``` console
233-
$ echo "$(docker exec gitea gitea generate secret SECRET_KEY)"
234-
```
235-
236-
> The reason for wrapping the command in an `echo` is because the `generate` command does not terminate the line so the value of the key has a tendency to run into the next Linux prompt.
237-
238-
Copy the value that is returned to the clipboard, then edit `~/IOTstack.env` to replace the right hand side of `GITEA_SECRET_KEY` with whatever is on the clipboard. Save your work then start the container again:
239-
240-
``` console
241-
$ docker compose up -d
227+
$ docker compose up -d gitea
242228
```
243229

244230
## container maintenance

0 commit comments

Comments
 (0)