open-im-server
open-im-server copied to clipboard
feat: docker compose lite version remove redundant components
What would you like to share?
目前依赖的docker过多,有一些其实没有必要,比如grafana prometheus 是否可以作为可选项而非必选项?
Additional information
No response
Hi @lucasjinreal,
Thank you for bringing up this issue. We understand your concern regarding the dependencies on Docker, specifically Grafana and Prometheus. We'll take your feedback into consideration and evaluate the necessity of these dependencies.
In the meantime, we would like to suggest a possible solution. You can make these dependencies optional instead of mandatory by providing an alternative configuration option. This way, users who require Grafana and Prometheus can still utilize them, while others can choose not to include them in their setup.
We'll discuss this internally and work towards implementing this option in a future release. Thank you for bringing this to our attention, and please let us know if you have any further questions or suggestions.
Similarly, perhaps you could pay attention to the examples in this repository: https://github.com/OpenIMSDK/openim-docker/tree/main/example
Inside, you might be able to find the files you need and replace them.
thanks for the attention. I am very new to openim, if there be an out of box docker enviroment which set grafana and Prometheus as optional that would be very useful and make it much more deliverable on any size of server.
IMHO, if it can runs on a 2GB mem server, it can be a killer as im services, since many developers might need more room to run their business code.
BTW, does there any timeline when will all storage migrate to mongodb? it would also be very nice if dependenices eliminate mysql
During yesterday's biweekly meeting, we had a discussion about this specific topic. The strategy of replacing MySQL with MongoDB will be gradually implemented in v3.5. I kindly request your attention and support regarding this matter.
thanks, is there an approximately release time on v3.5?
I would like to inform you that we are planning to release version 3.5 next week.
Awesome! Do u think once v3.5 release, the mem consume footprint can reduce?
@lucasjinreal yesp
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days.
This issue was closed because it has been stalled for 7 days with no activity.
/invite
We value close connections with our users, developers, and contributors here at Open-IM-Server. With a large community and maintainer team, we're always here to help and support you. Whether you're looking to join our community or have any questions or suggestions, we welcome you to get in touch with us.
Our most recommended way to get in touch is through Slack. Even if you're in China, Slack is usually not blocked by firewalls, making it an easy way to connect with us. Our Slack community is the ideal place to discuss and share ideas and suggestions with other users and developers of Open-IM-Server. You can ask technical questions, seek help, or share your experiences with other users of Open-IM-Server.
In addition to Slack, we also offer the following ways to get in touch:
We also have Slack channels for you to communicate and discuss. To join, visit https://slack.com/ and join our 👀 Open-IM-Server slack team channel.
Get in touch with us on Gmail. If you have any questions or issues that need resolving, or any suggestions and feedback for our open source projects, please feel free to contact us via email.
Read our blog. Our blog is a great place to stay up-to-date with Open-IM-Server projects and trends. On the blog, we share our latest developments, tech trends, and other interesting information.
Add Wechat and indicate that you are a user or developer of Open-IM-Server. We will process your request as soon as possible.
Could you please assist with the migration and integration of these items into the OpenIM Docker repository? Thank you.
- https://github.com/openimsdk/openim-docker