Commit Graph

9 Commits

Author SHA1 Message Date
gearnode
9640e4266a Refactor probo service
Signed-off-by: gearnode <bryan@frimin.fr>
2025-03-11 17:02:28 +01:00
gearnode
b41f417af6 Fix unauthenticate user not redirect to login page
fix #31

Signed-off-by: gearnode <bryan@frimin.fr>
2025-03-11 14:33:24 +01:00
gearnode
cc1c843d0a Refactor session loading management
Signed-off-by: gearnode <bryan@frimin.fr>
2025-03-11 12:36:49 +01:00
gearnode
019f76ecfd Refactor authentication handler
Signed-off-by: gearnode <bryan@frimin.fr>
2025-03-11 12:28:51 +01:00
gearnode
5bdc474aef Move coredata outside probo service
Signed-off-by: gearnode <bryan@frimin.fr>
2025-03-11 09:38:36 +01:00
gearnode
51fb5c9510 Update gqlgen code
Signed-off-by: gearnode <bryan@frimin.fr>
2025-03-11 09:14:01 +01:00
gearnode
c2bf3a42ed Simplify database schema
Signed-off-by: gearnode <bryan@frimin.fr>
2025-03-11 09:03:13 +01:00
gearnode
58eda95d93 Rewrite the global id system to include tenant id
The API should be aware of the tenant they are working on. Many solution
is possible like passing a header, adding the tenant id in each function
call, encode the tenant id in the GID.

I consider the header as a hack it force the client to keep in mind to
pass this header, having to returns an error in case of not defined
header and add a non standard header make the API more harder to use.

Passing the tenant id everywhere will be a good option but since Relay
impose to have node(id: ID!) Node interface it is not possible or by
hacking by wrapping node(id: ID!) Node in top query who getting the
tenant_id.

I finish by simpliy encode the tenant id directly in the object id, it
what AWS do too, it allow to always have the information, and it ensure
a right data isolation.

Signed-off-by: gearnode <bryan@frimin.fr>
2025-03-10 13:54:55 +01:00
gearnode
123a538d82 Embded frontend inside go binary
This will simplify the self hosting of the platform.

Signed-off-by: gearnode <bryan@frimin.fr>
2025-03-09 15:30:28 +01:00