From 3faf7dd1c85e89115077cf3da21153390f645d56 Mon Sep 17 00:00:00 2001 From: Lain Soykaf Date: Thu, 22 Oct 2026 13:04:06 +0400 Subject: [PATCH] docs: only list published admin-fe builds Only develop has a package. stable (2022) and the old tags have no Woodpecker config, so they get no build. --- docs/administration/CLI_tasks/frontend.md | 8 +------- docs/administration/frontends-management.md | 2 +- 2 files changed, 2 insertions(+), 8 deletions(-) diff --git a/docs/administration/CLI_tasks/frontend.md b/docs/administration/CLI_tasks/frontend.md index 6350c1f4e..064534384 100644 --- a/docs/administration/CLI_tasks/frontend.md +++ b/docs/administration/CLI_tasks/frontend.md @@ -78,25 +78,19 @@ Careful: This folder will be completely replaced on installation. ## Installing Admin-FE -Install the latest published `develop` build using the configured package URL: - === "OTP" ```sh ./bin/pleroma_ctl frontend install admin-fe --ref develop - # Or pin a release (replace with its exact tag): - ./bin/pleroma_ctl frontend install admin-fe --ref ``` === "From Source" ```sh mix pleroma.frontend install admin-fe --ref develop - # Or pin a release (replace with its exact tag): - mix pleroma.frontend install admin-fe --ref ``` -Use `--ref stable` for the latest published stable branch build, or replace `develop` with an exact published release tag to pin a version. The ref selects the package version in `https://git.pleroma.social/api/packages/pleroma/generic/admin-fe-builds/${ref}/latest.zip`; it must have a published package. The archive's `dist/` directory matches the default build directory, so no `--build-url` or `--build-dir` override is needed. +Builds come from the package registry: `https://git.pleroma.social/api/packages/pleroma/generic/admin-fe-builds/${ref}/latest.zip`. At the moment only `develop` is published. A `stable` branch or a release tag works as `--ref` once a build for it is published. ## Example installation for an unknown frontend diff --git a/docs/administration/frontends-management.md b/docs/administration/frontends-management.md index 44a0b82a0..9b8bf2caf 100644 --- a/docs/administration/frontends-management.md +++ b/docs/administration/frontends-management.md @@ -56,7 +56,7 @@ Due to aforementioned bug, preferred way of installing frontends in AdminFE is b ![screenshot of admin-fe with instructions on how to install a frontend](../assets/way_to_install_frontends.png) and filling in the fields. Unfortunately AdminFE does not provide the raw data necessary for you to fill those fields, so your best bet is to see what backend returns in browser's devtools or refer to the [source code](https://git.pleroma.social/pleroma/pleroma/-/blob/develop/config/config.exs?ref_type=heads#L742-791). For the most part, only **Name**, **Ref** (i.e. version) and **Build URL** fields are required, although some frontends might also require **Build Directory** to work. -Pleroma-FE and Admin-FE builds are downloaded from the generic package registry rather than GitLab job artifacts. For Admin-FE, set **Name** to `admin-fe` and **Build URL** to `https://git.pleroma.social/api/packages/pleroma/generic/admin-fe-builds/${ref}/latest.zip`. Set **Ref** to `develop` or `stable` for the latest published build of that branch, or to an exact published release tag to pin a version. Only refs with a published package are installable; an arbitrary Git ref is not enough. The archive contains a `dist/` directory, so use `dist` as **Build Directory** (the backend default). +Pleroma-FE and Admin-FE builds come from the package registry, not from GitLab job artifacts. For Admin-FE, set **Name** to `admin-fe`, **Ref** to `develop` and **Build URL** to `https://git.pleroma.social/api/packages/pleroma/generic/admin-fe-builds/${ref}/latest.zip`. Only refs with a published build can be installed; at the moment that is `develop`. ### Selecting default frontend