pardonblip static

Publishing guide

How CI pipelines publish to the static origin and how clients should reference published objects.

Path layout

PrefixContentsTTL
/b/Content-hashed application bundles1 year, immutable
/m/Media: images, fonts, video posters30 days
/releases/SDK archives with SHA-256 checksums1 day for index, 1 year for archives

Publishing from CI

Uploads go through the internal artifact pipeline, not this host. Once an object is promoted it becomes available here within a few seconds.

pb-artifacts publish \
  --app web-dashboard \
  --dir ./dist \
  --hash-names \
  --channel production

Referencing assets

Always reference hashed filenames. Unhashed paths are not cached and may be removed without notice.

<script src="https://static.pardonblip.com/b/web-dashboard/9c2e71f/app.js" defer></script>

Verifying downloads

$ curl -sO https://static.pardonblip.com/releases/pardonblip-sdk-2.4.1.tar.gz
$ curl -s https://static.pardonblip.com/releases/SHA256SUMS | sha256sum -c --ignore-missing

Limits