T

Deploy arikigame.com / deploy (push) Successful in 56s

Details

feat: initial import of arikigame.com static site

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>

2026-06-13 02:56:50 +01:00

.gitea/workflows

feat: initial import of arikigame.com static site

2026-06-13 02:56:50 +01:00

public

feat: initial import of arikigame.com static site

2026-06-13 02:56:50 +01:00

README.md

feat: initial import of arikigame.com static site

2026-06-13 02:56:50 +01:00

README.md

arikigame.com — Ariki game marketing site

Player-facing marketing site for Ariki, the game we build with Tinqs Studio.


URL	https://arikigame.com
Source	this repo (`ozan/ariki-website`, will move to `tinqs/ariki-website` when transferred)
Deploy	Gitea Actions — `.gitea/workflows/deploy.yml` on push to `main`
Hosting	AWS S3 `arikigame-com-website` + CloudFront `EDMY8TXLTDXLQ`
Owner	Ozan (Ariki Dev)

Layout

ariki-website/
├── public/          ← static files served at arikigame.com (today)
│   ├── index.html       (landing page)
│   ├── team-tool.html   (team-tool client)
│   ├── 404.html         (not-found)
│   ├── _next/           (Next.js framework)
│   ├── img/             (game screenshots, art)
│   └── team-tool/       (team-tool sub-app)
├── .gitea/workflows/
│   └── deploy.yml       (S3 sync + CloudFront invalidation)
└── README.md

Deploy

Push to main triggers .gitea/workflows/deploy.yml:

aws s3 sync public/ s3://arikigame-com-website/ --delete
aws cloudfront create-invalidation --distribution-id EDMY8TXLTDXLQ --paths "/*"

History

2026-06-13 — moved out of tinqs/studio/web/arikigame/ into its own repo (tinqs/ariki-website after ownership transfer). Game marketing no longer lives in the studio/platform monorepo.
2026-06-12 — last deploy from old location: chore: editor re-import metadata, sim checkpoints/telemetry, mountain QA script (commit 02ccbbf0a).
2026-05-22 — old tinqs/website Next.js company-landing app was deleted. The tinqs.com platform marketing moved to tinqs/studio/templates/home.tmpl (Go-served). Game marketing stays at arikigame.com (this site).

Future work

Replace public/ with a live Next.js app (currently a static export).
Add a web/ Next.js source tree; the workflow should next build then sync the out/ to S3.
Brand refresh: Cannarin's generated images in tinqs/design + Özlem's rebranding (TBD).

Verify a deploy

# Pipeline run
tinqs api /repos/ozan/ariki-website/actions/runs?limit=1

# Live content
curl -sI https://arikigame.com | head -3
PATH=/c/Program\ Files/Amazon/AWSCLIV2:$PATH aws s3 ls s3://arikigame-com-website/ | head