4130272855
Deploy arikigame.com / deploy (push) Successful in 56s
Migrated from tinqs/studio/web/arikigame/ into its own repo
(tinqs/ariki-website, currently under ozan/ for the bootstrap).
Game marketing is no longer hosted in the studio/platform monorepo.
What's in this commit:
- public/ — the live static site (Next.js static export, 39 files
served by S3 + CloudFront). Last deploy from old location
was 2026-06-12 (commit 02ccbbf0a in tinqs/studio).
- README.md — self-contained, no longer references the studio tree.
- .gitea/workflows/deploy.yml — same S3 sync + CloudFront invalidation
pipeline, triggered on push to main when public/** changes. S3 bucket:
arikigame-com-website, CF distribution: EDMY8TXLTDXLQ.
Verified:
- tinqs clone ozan/ariki-website (clone ok)
- aws s3 sync public/ s3://arikigame-com-website/ (deploy will run
on first push to main)
- curl https://arikigame.com (live content unchanged until first push)
Next steps after this commit lands:
1. Confirm the deploy workflow ran green on tinqs.com → check
/tinqs/ozan/ariki-website/actions/runs
2. Verify the live site still loads (S3 sync should be a no-op diff since
the source matches what's already deployed)
3. Transfer ownership: settings → transfer → tinqs org (if you want
it under tinqs/ariki-website instead of ozan/ariki-website)
4. Remove tinqs/studio/web/arikigame/ + .gitea/workflows/deploy-arikigame.yml
in a separate studio commit (depends on the deploy here working first)
Co-Authored-By: DeepSeek V4 Pro <noreply@deepseek.com>
6.3 MiB
2752x1536px
6.3 MiB
2752x1536px