[template request] SQL Server
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?
I'm not where where I can put this request so I apologise if it is in the wrong place.
Having to work around automatically exposed ports, more difficult backups, remembering docker compose file
Describe the solution you'd like
In the new service > database section having a SQL Server option (along with Postgres, MongoDB, etc) along with in built backups and an option to expose a port (disabled by default like Postgres)
Describe alternatives you've considered
- manually using docker compose to set up
- create backup script manually
- disabling port being exposed directly in the server
Additional context
No response
Will you send a PR to implement it?
Maybe, need help
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 request names no files or tests; start by comparing the existing Postgres, MongoDB, and other database entries in the new service database section. Done means a SQL Server option with built-in backups and port exposure disabled by default, matching the requested behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, sql
- Domain
- databases, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100