NASA-AMMOS / NASA-AMMOS/plandev
Enable running postgres on a port that isn't 5432
Open
Nobody has claimed this yet.
feature
- Dominant language
- Java
- Stars
- 128
- Forks
- 33
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 12
Description
Checked for duplicates
No - I haven't checked
Alternatives considered
No - I haven't considered
Related problems
Port 5432 is hard-coded in a number of places in the Aerie codebase. This makes it difficult to deploy Aerie on the same machine that's running another instance of postgres.
Describe the feature request
The database port environment variable should be used consistently across all services.
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
Search the Aerie codebase for hard-coded uses of port 5432 and identify how the database port environment variable is supplied to each service. Done means every service consistently uses that variable and Aerie can run against PostgreSQL on a non-default port.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, postgresql
- Domain
- backend, databases, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100