EnAccess / EnAccess/micropowermanager
[Feature Request]: Add different deployment scenarios to the documentation
- Dominant language
- PHP
- Stars
- 27
- Forks
- 19
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 27
Description
### Preflight Checklist
- [x] I have read the [Contributing Guidelines](https://github.com/EnAccess/micropowermanager/blob/main/CONTRIBUTING.md) for this project, if it exists.
- [x] I agree to follow the [Code of Conduct](https://github.com/EnAccess/micropowermanager/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [x] I have searched the [issue tracker](https://github.com/EnAccess/micropowermanager/issues) for a feature request that matches the one I want to file, without success.
### Problem Description
Currently, from the documentation the different deployment scenarios don't become very clear.
### Proposed Solution
Please add to the documentation a detailed description of the follow three scenarios.
- Fully Kubernetes (application and databases run as pods)
- Application Kubernetes with dedicated databases and Redis
- Stand-Alone server with dedicated databases and Redis
### Alternatives Considered
N/A
### Additional Information
_No response_
Contributor guide
Assessment
This issue has not been assessed yet.