From d6007f4be6d10fcf42f655e64fd572d54529b900 Mon Sep 17 00:00:00 2001 From: awiteb Date: Wed, 24 Apr 2024 00:21:51 +0200 Subject: [PATCH] Update README.md --- README.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 2ceea44..1e21c4f 100644 --- a/README.md +++ b/README.md @@ -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 ` 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 `