NginxProxyManager / NginxProxyManager/nginx-proxy-manager
Rebuild database using existing files
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 34.2k
- Forks
- 3.9k
- Avg merge
- 21h 12m
- Merged PRs (30d)
- 20
Description
Hello,
For some reason (my fault, tbh) nginx started with a fresh new database and overwrote the one i already had.
I still have plenty of other files (especially proxy entries) that i would like to use to rebuild the database automatically, rather than re-enter ~50 entries
It would be neat if NPM had that kind of feature
Contributor guide
No contributing guide indexed for this repository
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
No files, tests, or entry points are identified in the issue. Start by locating how Nginx Proxy Manager stores its database and proxy-entry files, then determine which existing files can be reconstructed safely. Done should mean the requested database rebuild works for the reported proxy entries without requiring manual re-entry.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nginx
- Domain
- backend, database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100