Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
4589e489a4
IPCR 1.8.1: Published images tab for many repositories. A filter (repository, alias, published tag; / to focus), sort by recently published or name, pages of 100 computed on the server; one line per repository, then one per manifest (tags on one digest together, Copy pull line), then one tag's pull lines and actions; what is open survives reloads, filter/sort/page kept in the URL. GET /admin/images takes ?q=&sort=&page=&per= and probes the staging registry for that page's repositories only; without page/per, the whole list as before (IPCR Forge admin page)
ecb8340834
IPCR: raise gateway and registry memory limits to 1G
c53299c0a8
IPCR 1.8.0: pin and follow. Dashboard tab Pinned: pin one image (ipns tag, ipfs CID, or any registry reference, imported), follow an IPNS name (ipcrteam.eth, or a path under it) to pin every image it publishes; releases keep what published images, pins, follows and pulls still use (gateway/pins.go)
27cd3fbc24
Apps/IPCR: ipcr 1.7.2 (watcher cleanup keeps tags pushed during a pass)
48dea6a29b
Watcher cleanup: keep a manifest a tag pushed during the pass still points at (1.2.3 then :latest, same digest, lost :latest)
1691e63020
Gitea workflow: push to the IPCR app on yunderalabs (ubuntu-latest runner, namespace token IPCR_PUSH_TOKEN), not the retired forge's staging registry
d7efef1d4a
Gitea workflow: push to the IPCR app on yunderalabs (ubuntu-latest runner, namespace token IPCR_PUSH_TOKEN); the forge's own runner and staging registry are gone
ab3f832e00
IPCR app: four services; push, staging, public pulls and the dashboard in one ipcrd process (push.go: in-process staging registry behind the gate; dashboard bound to AppShield's network)