Frontend for repertory, a tune-tracking program for old time musicians
  • JavaScript 66.4%
  • CSS 20.7%
  • HTML 12.9%
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
2026-09-21 15:21:36 -04:00
.gitignore Initial Commit 2026-06-09 15:04:27 -04:00
app.js Easier auth option 2026-09-21 15:21:36 -04:00
config.example.js Easier auth option 2026-09-21 15:21:36 -04:00
index.html Last cleanup commit 2026-08-07 17:25:32 -04:00
README.md Initial Commit 2026-06-09 15:04:27 -04:00
references_sample_values.csv Tunes CSV file 2026-09-11 10:31:01 -04:00
style.css Require key, instrument, tuning 2026-06-11 17:12:05 -04:00
tunes.csv Tunes CSV file 2026-09-11 10:31:01 -04:00

Repertory — frontend

Static single-page app for browsing and editing your tune repertory.

Local development

cp config.example.js config.js
# edit config.js — set apiUrl and apiKey to match your local .env
python -m http.server 8080
# open http://localhost:8080

config.js is gitignored and never deployed to S3. It pre-fills the connection bar so you don't have to type the API URL and key on every page load. See config.example.js for the full explanation of how this works.

Deployment

This is a fully static site (HTML + CSS + JS, no build step). Upload these files to your S3 bucket — config.js is intentionally excluded:

aws s3 sync . s3://your-bucket-name/ \
  --exclude "*" \
  --include "index.html" \
  --include "style.css" \
  --include "app.js"

In production, enter your API URL and key in the connection bar at the top of the page. These are saved in sessionStorage so you only need to enter them once per browser session.