To improve the user experience, I propose that we consolidate our self-host deployment configuration into a single docker-compose.yml file. This approach would offer several benefits:
Easier deployment for users, as they would only need to manage one file
Elimination of duplicated environment variables, which could be moved from example.env to docker-compose.yml
Automated folder creation by docker-compose, reducing the manual effort required from users
Also i don't think storing docker-compose.yml inside repository (that pulls from docker hub instead of building from source) is a good idea. In a few min. i will create pull request with those changes, its up to you if you commit them.
Use Case
No response
Code of Conduct
[X] I have searched for similar feature requests
[X] I have provided a clear and detailed explanation
Feature Description
To improve the user experience, I propose that we consolidate our self-host deployment configuration into a single docker-compose.yml file. This approach would offer several benefits:
Also i don't think storing docker-compose.yml inside repository (that pulls from docker hub instead of building from source) is a good idea. In a few min. i will create pull request with those changes, its up to you if you commit them.
Use Case
No response
Code of Conduct