hj/pleroma
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

docs: only list published admin-fe builds

Browse source 
Only develop has a package. stable (2022) and the old tags have no
Woodpecker config, so they get no build.
This commit is contained in:
Lain Soykaf 2026-10-22 13:04:06 +04:00
commit 3faf7dd1c8
No known key found for this signature in database
2 changed files with 2 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

8
docs/administration/CLI_tasks/frontend.md
View file

@ -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 <published-tag> with its exact tag):
./bin/pleroma_ctl frontend install admin-fe --ref <published-tag>
```
=== "From Source"
```sh
mix pleroma.frontend install admin-fe --ref develop
# Or pin a release (replace <published-tag> with its exact tag):
mix pleroma.frontend install admin-fe --ref <published-tag>
```
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

2
docs/administration/frontends-management.md
View file

@ -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