Decide on technologies that will be used #6

New issue

Closed

opened 2026-02-09 00:43:44 +00:00 by aaperis · 0 comments

aaperis commented

2026-02-09 00:43:44 +00:00

(Migrated from github.com)

As a developer
I want to have a clear decision on the technologies that I will use for the webapp
so that I can plan and execute accordingly.

AC:

The team discusses, proposes and decides on the framework for developing the UI and other tools that we'll use.
- We will need a OpenID Client (OIDC) implementation (server-side) for authenticating the user.
- Otherwise the UI does not need to be fancy.
Document decisions here.

Decisions:

for OIDC and fetching JsonWebToken to use in sda-download calls:
- we use sda-auth, modified
we use next.js/react for our website development
CSS bootstrap
Docker (and Docker compose for dev environment)
- which should comply with the kubernetes security standards used (one is non-root user)

Reasoning:

reuse what we have/cenbtralize authentication/authorization flows
possible need for modified JWTs later on (FEGA)
next.js provides all the tooling we need client+server side in the same framwework, familiar technology
bootstrap, it is user friendly and standard framework (maintainable)
one docker image, this is to be deployed in a kubernetes cluster

As a developer I want to have a clear decision on the technologies that I will use for the webapp so that I can plan and execute accordingly. AC: - The team discusses, proposes and decides on the framework for developing the UI and other tools that we'll use. - We will need a OpenID Client (OIDC) implementation (server-side) for authenticating the user. - Otherwise the UI does not need to be fancy. - Document decisions here. ## Decisions: - for OIDC and fetching JsonWebToken to use in sda-download calls: - we use sda-auth, `modified` - we use `next.js/react` for our website development - CSS bootstrap - Docker (and Docker compose for dev environment) - which should comply with the kubernetes security standards used (one is non-root user) ### Reasoning: - reuse what we have/cenbtralize authentication/authorization flows - possible need for modified JWTs later on (FEGA) - next.js provides all the tooling we need client+server side in the same framwework, familiar technology - bootstrap, it is user friendly and standard framework (maintainable) - one docker image, this is to be deployed in a kubernetes cluster