fin-site

Source of https://fin.jdkno.com, served by GitHub Pages from main (root). Pages are plain HTML: index.html, privacy/, terms/, refunds/, plus/ (the plans and prices page), support/, with images and fonts under web/.

README.md is not published: _config.yml excludes it from the Jekyll build that GitHub Pages runs. If a .nojekyll file is ever added (turning Jekyll off), this file would be published at /README.md; exclude it another way first.

Invite links of shared trips

https://fin.jdkno.com/trip/<token> (the token is 10 letters and digits) opens a shared trip in the Fin app:

• With Fin installed, iOS opens the app straight from the link, without loading a page. That needs .well-known/apple-app-site-association (it names the app, DNFZ3V3KN7.com.jdkno.fin, and the path /trip/*) and the app's applinks:fin.jdkno.com entitlement. _config.yml has include: .well-known because Jekyll leaves out folders that start with a dot; without it the file is not published and the links only open Safari. GitHub Pages serves the extensionless file as application/octet-stream, which iOS accepts. Check it with curl -i https://fin.jdkno.com/.well-known/apple-app-site-association (status 200, no redirect).
• Without Fin (or on a computer), GitHub Pages answers the unknown path with 404.html, which looks at the address: a link shaped like an invite shows the invitation (an "Open in Fin" button that uses the fin://trip/<token> address, the App Store button with "Coming soon", and the privacy and terms links); any other address shows "Page not found". The page is noindex and sends no referrer, so tokens stay out of search engines and other sites. Its status is 404, which only matters to search engines.
• When the app is on the App Store, replace the grey store button in 404.html with a link to its page, and remove the "Coming soon" pill.
• iOS fetches the association file through Apple's CDN when the app is installed and again now and then, so a change to it can take a day to reach phones. For a build run from Xcode, add ?mode=developer to the entitlement and turn on Settings > Developer > Associated Domains Development on the device.

Language of a page

Every page opens in the language the visitor last chose (kept in the browser), else the browser's language. A link can force one with ?lang=es or ?lang=en (for example https://fin.jdkno.com/terms/?lang=es); the app uses this to show its own language. The visitor can still switch with the EN / ES buttons. The script is the one at the end of each page.

Tutorial videos

tutorials/<lang>/<name>-<size>.mp4, with a poster tutorials/<lang>/<name>.jpg.

<lang>	en or es
<name>	apple-pay, notification, message or wallet-card-name (this one is vertical, 9:16)
<size>	720p for the app, 1080p for the web

Example URL: https://fin.jdkno.com/tutorials/es/message-720p.mp4

The files are H.264 with the index at the start (streamable). Keep them that way if you re-export.

Replacing a video

Overwrite the file(s) and commit. Git keeps every committed version forever, so each replaced video adds roughly its own size to the repository (a few MB to about 25 MB) even though the site only serves the new one. Unchanged files are never duplicated: committing other site changes does not add copies of the videos.

Keep an eye on the size with:

git count-objects -vH                      # size-pack is what a clone downloads
git rev-list --objects --all \
  | git cat-file --batch-check='%(objecttype) %(objectname) %(objectsize) %(rest)' \
  | awk '$1=="blob"' | sort -k3 -n | tail -20      # biggest files in all of history

Purging the old versions of the videos from history

Only needed when the repo has grown because videos were replaced. This rewrites history: every commit after the first one that touched tutorials/ gets a new hash, and the push must be forced. It is safe while you are the only person using the repo. Anyone else, or any other clone, must re-clone afterwards.

The idea: remove tutorials/ from the whole history, then add the current videos back in one commit. That leaves exactly one copy of each video.

1. Install the tool once: brew install git-filter-repo.

2. Save the videos you want to keep (the current files in your working copy):

   cp -R ~/development/fin-site/tutorials ~/tutorials-keep
   

3. Make a fresh clone to work in (filter-repo is meant for fresh clones, and it leaves your normal clone untouched as a backup):

   git clone https://github.com/jkano/fin-site.git ~/development/fin-site-purge
   cd ~/development/fin-site-purge
   

4. Remove the folder from all of history:

   git filter-repo --path tutorials --invert-paths
   

5. Put the current videos back and commit them once:

   cp -R ~/tutorials-keep tutorials
   git add tutorials
   git commit -m "Add tutorial videos"
   

6. Push the rewritten history. filter-repo removes the origin remote on purpose:

   git remote add origin https://github.com/jkano/fin-site.git
   git push --force origin main
   

7. Switch to the clean clone. Rename or delete the old fin-site folder after checking the site still loads, and use fin-site-purge (rename it to fin-site). Check the result with git count-objects -vH.

Things to know:

• GitHub does not free the space at once. The old objects stay reachable by their commit hashes for a while, and the repository size on GitHub shrinks after its own cleanup. If you need them gone sooner, ask GitHub Support to run garbage collection on the repository.
• Nothing about the live site changes: Pages republishes from the new main, and CNAME stays in the repo.
• The same recipe works for any folder: replace tutorials with the path to purge.