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

fix: install admin-fe from the package registry

Browse source
This commit is contained in:
Lain Soykaf 2026-10-22 12:02:52 +04:00
commit a03e5df39c
No known key found for this signature in database
5 changed files with 30 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -76,6 +76,28 @@ The resulting frontend will always be installed into a folder of this template:
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.
## Example installation for an unknown frontend
The installation process is the same, but you will have to give all the needed options on the command line. For example: