hasadna / hasadna/open_pension

Move the backend to nextjs

Open
#702 0 comments 0 reactions 0 assignees View on GitHub
Backoffice
Dominant language
TypeScript
Stars
17
Forks
16
PR merge metrics
No merged PRs in 30d

Description

This mean this will be a single service and much more easy to development/deploye and we'll get the benefit of nextjs as well: better router and more

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue proposes moving the backend to Next.js so the project becomes a single service with easier development and deployment. Start by mapping the existing backend and deployment structure, then define the migration scope and verify that the resulting service preserves current behavior and provides the stated routing and deployment benefits.

Written by the indexing model from the issue text.

Assessment

Tech stack
nextjs, typescript
Domain
backend, web-dev
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.