[Feature] Configuration options
- Dominant language
- TypeScript
- Stars
- 7.6k
- Forks
- 670
- PR merge metrics
- No merged PRs in 30d
Description
### Search before asking
- [X] I had searched in the [issues](https://github.com/labring/laf/issues?q=is%3Aissue) and found no similar issues.
### Feature Request
Can databases and storage be selected as optional configurations? Some applications require direct connection to other databases and do not require the use of LAF databases. Only the coding part is needed
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or configuration entry points. Start by locating how database and storage services are configured and initialized, then determine the configuration boundary for making both optional. Done means an application can use only the coding functionality without requiring LAF databases or storage, with the existing configuration and startup behavior covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100