You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We would like to reduce the spread of the project to have to maintain and work on a single app for the client.
Project preparation:
move to pnpm for package management: lighter and faster than yarn and also supports workspaces (will be useful in the future maybe) build: migrate to pnpm #211
Progressively update the configurations of the project to prepare it
What's the difference between "use @tanstack/react-router" and "migrate account to tanstack router". Are you referring to the code, then to the deployment?
We would like to reduce the spread of the project to have to maintain and work on a single app for the client.
Project preparation:
pnpm
for package management: lighter and faster thanyarn
and also supports workspaces (will be useful in the future maybe) build: migrate to pnpm #211Migration to `@tanstack/react-router:
Use
@tanstack/react-router
instead ofreact-router-dom
as it allows to split on routes and managing routes with typesafety is awesome.@tanstack/react-router
graasp.org
instead ofaccount.graasp.org
Making the project single origin
We want to host the project on a single domain, to:
simplify cookie management and make it more secure, no more (.graasp.org cookies)
remove the need for CORS
streamline the devlopment and usage of common layouts in a single project
Backend should be reachable at
graasp.org/api
/api
requests to the backendmigrate player here
migrate analytics here
migrate builder here
builder.graasp.org
,auth.graasp.org
,player.graasp.org
should redirect to the path equivalents using the load-balancerlibrary should be served on a subpath too
We should be able to remove the CORS for the core endpoints since all the trafic should be from the
graasp.org
domain.The text was updated successfully, but these errors were encountered: