Skip to content

Latest commit

 

History

History
21 lines (14 loc) · 1.25 KB

README.md

File metadata and controls

21 lines (14 loc) · 1.25 KB

Install and run the devcon app

To start the devcon app: yarn install in monorepo/lib yarn install yarn dev

Optional: RECOIL_DUPLICATE_ATOM_KEY_CHECKING_ENABLED=false in .env to remove some warnings

Devcon API

The devcon app is served by the devcon api, which is hosted on app.devcon.org.

For outside contributors (e.g. not from the devcon team): Running the API locally is not recommended/difficult, as it requires a lot of setup and access to the devcon database.

PWA cache/install strategy:

  • Precache the app skeleton (basic html/js/css; layout, header, footer, etc.); this allows for fast installation time
  • Cache event data at runtime because these datasets are huge (20-30mb) - if these were precached it would extend the precache step significantly, making it very hard to ship updates fast and reliably
  • Event data is permanently cached by the service worker using a "version identifier", which is retrievable via the devcon api - whenever event data changes on the backend, the version returned by the devcon api will increment/change - the client can then ping this "version endpoint" instead of the underlying data to efficiently check for updates - if the client version is different from the backend version, the client can then redownload all data.