Fix API meta public origin #51
No reviewers
Labels
No labels
activitypub
actor
admin
ai-safety
article
articles
atproto
bug
cli
configuration
content
dev-environment
docker
enhancement
feature
federation
fediverse
forgejo
garage
health
how-to
logging
markdown
mastodon
media
navigation
opengraph
passkeys
preview
priority:medium
production
release
rendering
s3
settings
setup
status:active
status:done
status:inprogress
technical
webauthn
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
erik/slugkit.com!51
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "task-9fb83661-api-meta-public-origin"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
ACTIVITYPUB_PUBLIC_ORIGINwhen configured.site.url,api.baseUrl, andapi.openapiUrlfor proxied production requests.Verification
npm run buildnpm testNotes
This fixes the production
/api/v1/metaissue observed after deploying0.1.33, where metadata reportedhttp://localhost:3000and proxied HTTP URLs despiteACTIVITYPUB_PUBLIC_ORIGIN=https://slugkit.combeing set.Review summary
The PR directly addresses the API meta public-origin bug by passing the runtime environment into meta generation and making
ACTIVITYPUB_PUBLIC_ORIGINthe canonical public origin when configured.Acceptance criteria
ACTIVITYPUB_PUBLIC_ORIGIN—createApiMetaResponsenow reads and appliesACTIVITYPUB_PUBLIC_ORIGIN.site.url,api.baseUrl, andapi.openapiUrl— proxiedhttp://slugkit.com/api/v1/metatest with public origin expects HTTPS URLs.npm run buildandnpm testpass — PR body reports both checks passed.Blocking issues
Warnings
Verdict
Approved.