3f77777c4b
FreeSewing now uses NodeJS 18 -- specifically lts/hydrogen -- for its development. There is no specific reason to run 18, things will still work in 16 (lts/gallium) but Vercel who hosts/builds our sites will be dropping support for Node 16 in about 6 months, so since we're gearing up for a new major release (v3) this is the best time for us to also move to Node 18. |
||
|---|---|---|
| .. | ||
| openapi | ||
| prisma | ||
| public | ||
| scripts | ||
| src | ||
| tests | ||
| .gitignore | ||
| build.mjs | ||
| Dockerfile | ||
| example.env | ||
| local-config.mjs | ||
| nodemon.json | ||
| package.json | ||
| README.md | ||
FreeSewing backend
This is a work in process to port the v2 backend to a new v3 backend.
It will be based on Express using Prisma with a SQLite database. Watch this space.
Permission levels
There are two different models to authenticate, as user, or with an API key.
The API keys have more granularity, their permission levels are:
0: No permissions. Can only login but not do anything (used for testing)1: Read access to own people/patterns data2: Read access to all account data3: Write access to own people/pattern data4: Write access to all own account data (this is theuserrole)5: Read access to people/pattern data of all users (this is thebughunterrole)6: Read access to all account data of all users7: Read access to all account data of all users + Write access for specific support functions (this is thesupportrole)8: Write access to all account data of all users (this is theadminrole)
User roles map to these permission levels as such:
user: 4 (this is everybody)bughunter: 5 (a small group of people, less than 10)support: 7 (a small number of trusted collaborators, less than 5)admin: 8 (joost)
When using an API key above level 4, you need the following roles:
- 5: Requires bughunter, support, or admin
- 6,7,: Requires support or admin
- 8: Requires admin