Add external domains for databases
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 37.4k
- Forks
- 3k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 73
Description
What problem will this feature address?
Adding external domains for databases will allow multiple databases to be exposed publicly on the same port. Currently only 1 db can be exposed on a port as the external address uses the ip address. This will also help with ergonomics so people aren't juggling a bunch of postgres instances with different port numbers and no other naming. This is also a feature supported by CapRover.
Describe the solution you'd like
A domain tab exactly like the applications domain tab.
Describe alternatives you've considered
Current workaround is to assign different ports for each db or use the AI tool to create the db as a compose application. Personally I recommend just setting up databases as regular application.
Additional context
No response
Will you send a PR to implement it?
No
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
Start by locating the existing application domain tab and the database configuration and exposure entry points in the repository. Compare how application domains are represented with the current database IP and port handling, then verify that multiple databases can use domain-based external addresses without requiring distinct ports.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose, postgresql, typescript
- Domain
- databases, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100