Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Optimize the Docker architecture #185

Open
timerring opened this issue Mar 9, 2025 · 0 comments
Open

[Feature] Optimize the Docker architecture #185

timerring opened this issue Mar 9, 2025 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@timerring
Copy link
Owner

Is your feature request related to a problem? Please describe.

In current version, the docker is comprised of the record module(which I use the blrec lib) and postprocess module, but this is not the best practice of docker.

In fact, the Docker container should be stateless. This means it's easy to check if the service is still operational. Also, files generated by the services shouldn't be stored within the Docker container itself. This is to avoid potential file loss in case the service goes down or other unforeseen circumstances occur.

Describe the solution you'd like

In the next version, we should separate the recording and processing modules into different Docker containers, and have both of them mount the same volume. This way, we can retain the files even if the service goes down. Additionally, we can make full use of webhooks and attempt to use Kubernetes for composition to manage the services more effectively.

@timerring timerring self-assigned this Mar 9, 2025
@timerring timerring added the enhancement New feature or request label Mar 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant