jrmi / airboardgame-back Goto Github PK

With a siteId we can initialize a JSON store and a file store and by site to allow sharing same instance of backend.

To allow easy box behaviour customization, we can use declare hooks at box creation to be able to modify input or output data.

Some use cases:

• Allow only owner to modify a resource without having to create spc for each verb (i.e. update, delete)
• filter list query only for public/published or owned records
• Delete expired entries on request

See:

• https://codeforgeek.com/encrypt-and-decrypt-data-in-node-js/
• https://github.com/chris-rock/node-crypto-examples
• https://github.com/chris-rock/node-crypto-examples

Requirements:

• Easy to use in dev mode
• Easy to use in pipeline
• Allow multiple hostname live on same siteId (ex: For deploy preview for instance)
• Allow same hostname live on multiple siteId (Try on dev then try on prod or have multiple server)

Steps:

1. We register the site via an API and get an api key
2. We crypt "something" with the key to pass a challenge and put in setup ? Or we crypt the setup.py file with the secret key ?
3. When we visit the site, since the browser call an endpoint, the server try to access the referer (or whatever specified in query) and load the setup from it ?

Private box are box only for authenticated user.
To add private box we need:

• To create a store wrapper with that API:
  • constructor(store) => keep the store internally for further references
  • getStore(user) => return an object with original store API but box id is rewriten if the box is "private" (we can rewrite box id like that _${userID}_${boxId}) to access transparently to user specific store. boxId starting with _ are internal only.
• Allow to create private store by using the already defined personnal box options
• To use that wrapper everywhere a store is used:
  • In CRUD views
  • In execute middleware context

• To clean expired entries for example
• To delete unused images