Asking before writing anything, since PRs are disabled and I'd rather not spend your review
time on a patch you don't want.
The gap: Run it needs an S3-compatible bucket and a working AWS credential chain before
celld will start. That's correct for operators, but it's a wall for anyone who just wants to
see celld serve something before deciding whether to invest in it. Install gets you a binary
in seconds; the first actual run is a much bigger step.
What I'd propose: a short ## Hosted section between Run it and Operate a fleet — five
or six lines plus a deploy button. One click provisions a bucket, wires CELLD_BUCKET,
S3_ENDPOINT, AWS_REGION and the access keys into the container, and runs the published
ghcr.io/denoland/celld image. celld deploy from a local checkout into the same bucket is
unchanged, so it's an on-ramp to the documented workflow rather than a parallel one.
No fork and no wrapper image — it runs your published release image as-is. I'd mark it
community-maintained, not an official Deno build.
Disclosure: I maintain the template and Railway pays template authors a share of what
deployments spend, so I'm not a neutral party here. Judge it on whether it's useful to people
evaluating celld.
If you want it, I'll send a git format-patch to ry@deno.com under the CLA terms in the README.
If not, closing this costs you one click and I won't push further.
Asking before writing anything, since PRs are disabled and I'd rather not spend your review
time on a patch you don't want.
The gap:
Run itneeds an S3-compatible bucket and a working AWS credential chain beforecelld will start. That's correct for operators, but it's a wall for anyone who just wants to
see celld serve something before deciding whether to invest in it.
Installgets you a binaryin seconds; the first actual run is a much bigger step.
What I'd propose: a short
## Hostedsection betweenRun itandOperate a fleet— fiveor six lines plus a deploy button. One click provisions a bucket, wires
CELLD_BUCKET,S3_ENDPOINT,AWS_REGIONand the access keys into the container, and runs the publishedghcr.io/denoland/celldimage.celld deployfrom a local checkout into the same bucket isunchanged, so it's an on-ramp to the documented workflow rather than a parallel one.
No fork and no wrapper image — it runs your published release image as-is. I'd mark it
community-maintained, not an official Deno build.
Disclosure: I maintain the template and Railway pays template authors a share of what
deployments spend, so I'm not a neutral party here. Judge it on whether it's useful to people
evaluating celld.
If you want it, I'll send a
git format-patchto ry@deno.com under the CLA terms in the README.If not, closing this costs you one click and I won't push further.