deray·edge

a small, boring static asset endpoint

Fetching a file

Paths map directly onto the on-disk layout. There is no rewriting and no index generation, so a path either exists or returns the not-found page.

https://cdn.deray.space/f/<bucket>/<name>
https://cdn.deray.space/f/type/inter-v13-latin.woff2
https://cdn.deray.space/f/docs/2026-field-notes.pdf

Immutable paths

Anything under an eight-character content hash is served with a one-year cache lifetime and will never change contents. Prefer these in anything you publish.

https://cdn.deray.space/i/<hash8>/<name>
https://cdn.deray.space/i/9f3ab21c/sprite.svg

Buckets in use

BucketContentsRoughly
typeSubsetted web fonts, woff2 only40 files
iconSVG sprites and favicons120 files
docsPDFs meant to outlive their project pages90 files
imgPhotographs, long edge capped at 2560 px600 files

Ranges and compression

Byte ranges are honoured, which matters for the PDFs — most readers fetch the cross-reference table first and then jump. Text-ish types are compressed on the fly; already-compressed formats are passed through untouched.

Publishing

Uploads are rsync over SSH from two known keys. There is no upload form, and adding one is not on the list. If you need something published, ask the person who sent you this link.

Hotlinking. Fine, within reason. This is one modest machine on a shared uplink — if a page you run starts pulling tens of gigabytes a day, please mirror the files instead.