hanzoai/social
2
0
Fork 0
mirror of https://github.com/hanzoai/social.git synced 2026-10-17 11:18:21 +00:00
Code Issues Packages Projects Releases Wiki Activity

social.hanzo.ai publishes as a site

Browse Source 
The social Deployment is a SPA server over this repo's dist and nothing else:
no SPA_* config, no API of its own (that is api.hanzo.ai). So the export is
published to the Sites plane as `social`, s3://hanzo-sites/hanzo/social, for the
edge to serve with no pod. The build gate already produces dist in the same
job, so the lane names no build of its own.

Checked in headless Chromium: the export on social.hanzo.ai renders what the pod
renders.

Co-authored-by: Hanzo Dev <[email protected]>
This commit is contained in:
zeekay
2026-09-19 10:25:07 -07:00
co-authored by Hanzo Dev
parent 9ee5c31d90
commit 9c7bdaebf0
1 changed files with 9 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
hanzo.yml
+9
View File
@@ -30,3 +30,12 @@ images:
# No build_secrets, and none belong here. Every credential that names a
# person is minted by hanzo.id at sign-in; every credential that names a
# network is sealed in KMS and read only by the publisher, server-side.
# social.hanzo.ai is bytes: the export is the whole product and its API is
# api.hanzo.ai. The site lane publishes the `build` gate's dist to
# s3://hanzo-sites/hanzo/social, where the edge serves it with no pod. The image
# lane above goes when the social Deployment does.
site:
slug: social
dir: dist
on: [main]