1
0
Fork 0
freesewing/sites/backend
dependabot[bot] 8357e3ccac
build(deps): bump @aws-sdk/client-sesv2 from 3.476.0 to 3.477.0
Bumps [@aws-sdk/client-sesv2](https://github.com/aws/aws-sdk-js-v3/tree/HEAD/clients/client-sesv2) from 3.476.0 to 3.477.0.
- [Release notes](https://github.com/aws/aws-sdk-js-v3/releases)
- [Changelog](https://github.com/aws/aws-sdk-js-v3/blob/main/clients/client-sesv2/CHANGELOG.md)
- [Commits](https://github.com/aws/aws-sdk-js-v3/commits/v3.477.0/clients/client-sesv2)

---
updated-dependencies:
- dependency-name: "@aws-sdk/client-sesv2"
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
2023-12-20 04:53:08 +00:00
..
openapi
prisma feat(backend): Add height field to cset model 2023-10-20 10:42:43 +02:00
public
scripts
src fix(backend): Don't escape URLs. See #5516 2023-11-26 15:07:40 +01:00
tests chore(backend): Thanks prettier, real nice 2023-10-17 18:18:03 +02:00
.gitignore
build.mjs feat(shared): Add dynamic OG images 2023-11-03 15:36:09 +01:00
Dockerfile
example.env
local-config.mjs
nodemon.json
package.json build(deps): bump @aws-sdk/client-sesv2 from 3.476.0 to 3.477.0 2023-12-20 04:53:08 +00:00
README.md
test.sh feat(backend): Support for generating images 2023-11-03 12:58:58 +01:00

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 data
  • 2: Read access to all account data
  • 3: Write access to own people/pattern data
  • 4: Write access to all own account data (this is the user role)
  • 5: Read access to people/pattern data of all users (this is the bughunter role)
  • 6: Read access to all account data of all users
  • 7: Read access to all account data of all users + Write access for specific support functions (this is the support role)
  • 8: Write access to all account data of all users (this is the admin role)

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