From 57699bd3b7b634a7a0c7c1edea21ea7798d27149 Mon Sep 17 00:00:00 2001 From: wackbyte Date: Mon, 19 Jun 2023 22:39:05 -0400 Subject: [PATCH] chore: make all intra-site links not use a specific domain # Conflicts: # v1.19/index.md --- admin/installation.md | 6 +++--- developer/RELEASE.md | 4 ++-- index.md | 4 ++-- 3 files changed, 7 insertions(+), 7 deletions(-) diff --git a/admin/installation.md b/admin/installation.md index 3cf9e019..1cb6aa6b 100644 --- a/admin/installation.md +++ b/admin/installation.md @@ -154,7 +154,7 @@ services: > **NOTE:** this guide assumes that you'll host on the server with the domain git.example.com. First, download the Forgejo binary for your CPU architecture and maybe verify the GPG signature, -as described on [the Forgejo download page](https://forgejo.org/download/). +as described on [the Forgejo download page](/download). Next, copy the downloaded Forgejo binary to `/usr/local/bin/` (renaming it to just "forgejo") and make it executable: @@ -335,7 +335,7 @@ The following changes are recommended if dealing with many large files: PROTOCOL = sendmail FROM = "Forgejo Git" ``` -- By default Forgejo will listen to the port 3000 but that can be [changed to 80 with HTTP_PORT](../config-cheat-sheet) like this: +- By default Forgejo will listen to the port 3000 but that can be [changed to 80 with HTTP_PORT](config-cheat-sheet) like this: ```ini [server] HTTP_PORT = 80 @@ -351,7 +351,7 @@ You can test sending a mail by clicking the user button on the upper right of th ## General hints for using Forgejo Sometimes you may want/need to use the Forgejo -[command line interface](https://forgejo.org/docs/latest/admin/command-line/). +[command line interface](command-line). Keep in mind that: - You need to **run it as `git` user**, for example with `$ sudo -u git forgejo command --argument` diff --git a/developer/RELEASE.md b/developer/RELEASE.md index a10d4027..39a8b5b8 100644 --- a/developer/RELEASE.md +++ b/developer/RELEASE.md @@ -89,12 +89,12 @@ The release is built from https://codeberg.org/forgejo-integration/runner which ### Securing the release token and cryptographic keys -For both the Forgejo runner and Forgejo itself, copying and signing the release artifacts (container images and binaries) happen on a Forgejo isntance running [behind a VPN](https://forgejo.org/docs/next/developer/infrastructure/#octopuce) to safeguard the token that has write access to the Forgejo repository as well as the cryptographic key used to sign the releases. +For both the Forgejo runner and Forgejo itself, copying and signing the release artifacts (container images and binaries) happen on a Forgejo isntance running [behind a VPN](infrastructure#octopuce) to safeguard the token that has write access to the Forgejo repository as well as the cryptographic key used to sign the releases. ### Website update - Restart the last CI build at https://codeberg.org/forgejo/website/src/branch/main/ -- Verify https://forgejo.org/download/ points to the expected release +- Verify [https://forgejo.org/download/](/download) points to the expected release - Update the [documentation link to the latest version](https://codeberg.org/forgejo/website/src/commit/e63c6f8ab64876b10b86de1d18162b6ccb87bd99/.woodpecker.yml#L35) - Manually try the instructions to work diff --git a/index.md b/index.md index 1cca103f..ffc616b3 100644 --- a/index.md +++ b/index.md @@ -3,9 +3,9 @@ layout: '~/layouts/Markdown.astro' title: 'Forgejo v1.20 documentation' --- -- [What is Forgejo?](https://forgejo.org/) +- [What is Forgejo?](/) - [Installation](admin/installation) -- [FAQ](https://forgejo.org/faq/) +- [FAQ](/faq) - [Administrator guide](admin) - [User guide](user) - [Developer guide](developer)