Skip to content

Latest commit

 

History

History
39 lines (26 loc) · 1.05 KB

README.md

File metadata and controls

39 lines (26 loc) · 1.05 KB

peated

Schema Notes:

  • Do we need the bottle series? Also sometimes series are for specific retailers, does that matter? e.g. Bottled for Healthy Spirits, Bottle #1345
  • Should we have bottled dates or just bottled years?
  • Is CaskType possible to constrain to an enum? Same question for Category.
  • Tags make up a lot of flavor profiles - should things like the way its coal fired be focused on tasting notes more so than bottle or distiller information?

https://www.whiskybase.com/ is a good example of what the kind of db we need. Initial scraper to populate a DB (will need further enriched with other sources) is in scraper

Dev

Bootstrap the environment:

docker-compose up -d
npm run setup

Note: If you need to tweak default settings, cp .env.example .env and go to town.

Create a local user to avoid setting up Google credentials:

npm run user:create e -w apps/api

Run the dev server, which spins up both the web and the api services:

npm run dev

NX is used to manage the monorepo, e.g.

npx nx run-many -t build