awiteb/forgejo-conf-files
1
Fork 0
Code Issues Pull requests Releases Activity Actions

Update README.md

Browse source
This commit is contained in:
awiteb 2024-04-24 00:21:51 +02:00
parent 51396a14ef
commit d6007f4be6
1 changed files with 3 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
README.md
View file

@ -28,8 +28,7 @@ The instance will be available at `http://0.0.0.0:8080` so proxy it to your doma
### Patch
Stop the instance using `docker-compose rm -s -f` then remove the forgejo image using `docker rmi -f <IMAGE ID>` then rerun the instace using `docker-compose up -d`
> TIP
>
> [!TIP]
> You can use `just update_patch`
### Major,Mirror
@ -39,7 +38,7 @@ by running `docker-compose rm -s -f` and then run `docker-compose up -d` again.
## Restaring
When you want to restart the forgejo, do not run `docker-compose restart` I see that makes some changes to the configuration, so it's better to remove the containers by running `docker-compose rm -s -f` and then run `docker-compose up -d` again.
> TIP
> [!TIP]
>
> You can use `just restart`
@ -50,7 +49,7 @@ Is using sqlite3, and is more than enough for personal use.
The data is stored in the [forgejo](./forgejo) directory and [forgejo-runner](./forgejo-runner) directory, so you can backup them.
The containers are stateless, so it's do not store any data.
> TIP
> [!TIP]
>
> You can use `just backup <BACKUP NAME>`