OpenEnergyPlatform / OpenEnergyPlatform/oeplatform
Provide container based production deployment setup
Open
@jh-RLI is already working on this.
Since May 18, 2026.
deployment
Infrastructure
NFDI
- Dominant language
- Python
- Stars
- 65
- Forks
- 29
- Avg merge
- 15h 25m
- Merged PRs (30d)
- 32
Description
Description of the issue
We will soon migrate our infrastructure hosting provider. Currently we use a quite stable but manually configured infrastructure composed of multiple services that run in several zones. In the future we want to further automate the infrastructure setup to ease the deployment of the full oeplatform stack for all individual instances of the OEP out there.
Ideas of solution
To start of we need to test out what container solution / software we want to use.
- k8n -> to complex and overkill; The OEP is not expected to serve > 10k simultaneous users and will for sure not have millions of users. This is simply no realistic use case.
- podman -> seems to be the best fit: Most secure, using systemd; the downside is not the best developer experience, as everything must be set up without a GUI
- caprover: best mix of both worlds but less secure and based on docker swarm. It offers a nice GUI and makes it very easy to get started. Debugging can be quite annoying if anything breaks on a lower level (DNS etc.)
Workflow checklist
- I am aware of the workflow in
CONTRIBUTING.md
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.
Assessment
This issue has not been assessed yet.