docs: add custom registries basic documentation

cmd/serve/front/src/routes/(main)/registries/+error.svelte

@@ -8,7 +8,7 @@
 
 <Breadcrumb
 	segments={[
-		{ path: routes.targets, title: l.translate('breadcrumb.registries') },
+		{ path: routes.registries, title: l.translate('breadcrumb.registries') },
 		l.translate('breadcrumb.not_found')
 	]}
 />

docs/.vitepress/config.mts

@@ -51,6 +51,10 @@ export default defineConfig({
               },
             ],
           },
+          {
+            text: "Registries",
+            link: "/reference/registries",
+          },
           {
             text: "Applications",
             link: "/reference/applications",

docs/guide/installation.md

@@ -68,6 +68,8 @@ You probably want to expose seelf itself on an url without a port and with a val
 
 ::: warning
 If you choose to expose **seelf** with the local target, you **should never** delete the target or things may break.
+
+If it happens, you can map the port `8080` to access your seelf instance (on the root domain and port) and reconfigure the target. Once done, you can remove the ports section since seelf will be exposed by the proxy.
 :::
 
 To do this, we recommend to use the [docker compose installation](#with-compose) and add the missing parts.

docs/reference/registries.md

@@ -0,0 +1,5 @@
+# Custom registries
+
+If you need to deploy images hosted on private registries (such as ones using the [registry](https://hub.docker.com/_/registry) image), you can declare them on **seelf** on the appropriate page.
+
+Registries are **shared** across [targets](/reference/targets) and are used during the deployment process as soon as they are configured.