pgadmin-org / pgadmin-org/pgadmin4
Migration to a production-ready server (Waitress), replacing Flask for improved performance and reliability.
Open
Nobody has claimed this yet.
Housekeeping
- Dominant language
- Python
- Stars
- 3.8k
- Forks
- 891
- Avg merge
- 4d 7h
- Merged PRs (30d)
- 8
Description
This issue has no description.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names a migration from Flask to Waitress but provides no files, tests, entry points, or acceptance criteria. Start by locating the current Flask server startup and deployment configuration, then determine which existing behavior must remain available through Waitress. Done should mean the migration is implemented with the intended performance and reliability improvements verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- flask, python
- Domain
- backend, devops
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100