richjohnrambo
2b631ab176
fix: harden websocket heartbeat under load
2026-09-30 17:36:33 +08:00
richjohnrambo
3bb6774786
fix: protect publish path from mysql exhaustion
2026-09-27 18:35:54 +08:00
richjohnrambo
ce3250be64
fix: harden multi-pod delivery and load verification
2026-09-27 03:37:32 +08:00
richjohnrambo
f898a7171c
feat: batch kafka message persistence
2026-09-24 22:45:07 +08:00
richjohnrambo
aa9f562e1e
refactor: retire legacy tinode database routing
2026-09-23 17:04:30 +08:00
richjohnrambo
9ddf6ec5ee
fix shared-db tenant runtime gaps
2026-09-22 19:28:33 +08:00
richjohnrambo
e4416da04a
fix im server shared database config
2026-09-22 16:45:24 +08:00
Your Name and Claude Sonnet 5
b30cce950a
fix(docker): mirror tinode's own log output to stdout
...
Confirmed live: /var/log/tinode.log-only redirection meant Loki never
received a single real tinode runtime log line (election, rehash,
connection, error output) since the container started -- Promtail
collects standard container stdout/stderr, not files written inside
the container. Every Pod's collected log was just this script's own
"NO_DB_INIT=true: skipping..." init line, nothing from tinode itself.
Now more consequential with native Cluster enabled: failover/rehash
state transitions were completely invisible to the normal Grafana/Loki
monitoring path, visible only via manual kubectl exec.
tee mirrors to both stdout (collected) and the file (still readable via
kubectl exec). PIPESTATUS[0] is required since a bare $? after a pipe
would report tee's exit status, not tinode's -- which also let this
drop the now-redundant "tail last 200 lines to stderr on crash" block,
since the full live stream already went to stdout throughout the run.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com >
2026-09-21 20:23:25 +08:00
richjohnrambo
407842db91
fix: prepare native cluster deployment
2026-09-21 13:52:34 +08:00
richjohnrambo
b9aaccc830
fix: update uid encryption key defaults
2026-09-17 16:59:47 +08:00
richjohnrambo
15abc1b6e8
fix: bake test middleware config
2026-09-14 23:59:35 +08:00
richjohnrambo
0cf2fb61a7
fix: restore docker middleware env config
2026-09-14 23:52:00 +08:00
richjohnrambo
40510a616e
fix: bake test middleware config into image
2026-09-14 23:28:07 +08:00
richjohnrambo
7196d0c839
fix: include jpush handler in docker config
2026-09-14 21:09:28 +08:00
richjohnrambo
9159ec7fc7
feat: add IM service health and metrics endpoints
2026-09-09 14:24:40 +08:00
richjohnrambo
aae13c9265
feat: load oss media config from sys config
2026-09-08 22:19:00 +08:00
richjohnrambo
35da3025a3
fix: 恢复IM内部接口默认启动配置
2026-09-07 16:02:56 +08:00
richjohnrambo
c68c5ac038
fix: 补齐IM治理功能启动配置
2026-09-07 12:06:46 +08:00
richjohnrambo
160d33c759
Reduce Kafka publish latency for messages
2026-09-07 11:33:50 +08:00
richjohnrambo
0f1c1f9255
fix: enable local kafka docker integration
2026-09-04 11:57:38 +08:00
richjohnrambo
7193ba2316
fix: 完善后台组织内部查询
2026-09-03 17:11:36 +08:00
richjohnrambo
ba06ee3472
chore: use internal admin service url
2026-08-28 01:08:51 +08:00
richjohnrambo
a54ddfa548
chore: use public admin internal api
2026-08-28 00:48:42 +08:00
richjohnrambo
94552a84b4
chore: configure internal api auth
2026-08-28 00:40:40 +08:00
richjohnrambo
84439d63cb
chore: configure test kafka
2026-08-28 00:35:10 +08:00
richjohnrambo
ca734a48ab
feat: support kafka scram auth
2026-08-28 00:31:08 +08:00
richjohnrambo
5cc6eebc1a
feat: add kafka admin integration
2026-08-28 00:05:54 +08:00
richjohnrambo
c020171e52
fix: restore mysql docker build
2026-08-25 22:17:59 +08:00
richjohnrambo
f900a08a01
feat: add redis cache and fanout support
2026-08-25 20:54:03 +08:00
richjohnrambo
07376c70e3
fix: stabilize im server startup and p2p topic scans
2026-08-24 16:20:02 +08:00
richjohnrambo
c09ea2ac53
fix: stabilize container validator startup
2026-08-20 13:28:28 +08:00
Your Name
57274778b5
接入Gitea Actions蓝绿部署：本地源码构建替代release下载，接入租户注册表迁移
...
- 新增docker/tinode/Dockerfile.build：从本仓库源码编译server/tinode-db/
apply_hotgo_tenant_db，替代原Dockerfile下载GitHub release的方式(否则
workbench/组织架构/会议等改造代码永远不会真正跑起来)
- config.template补上连接池设置(max_open_conns等，此前im_server踩过注册卡死
的坑)，并启用tenant_db_routing+tenant_registry_db=hotgo，对应本仓库自带
tinode.conf里的默认约定，单租户场景下会透明落回同一个tinode库
- entrypoint.sh在init-db之后追加执行apply-hotgo-tenant-db，幂等地建好/
升级hotgo租户注册表及tinode库里的workbench/组织架构/会议/日报/信箱等新表
- 新增.gitea/workflows/deploy.yml，复用服务器上已有的蓝绿部署脚本
2026-08-15 14:08:07 +08:00
richjohnrambo
c2076721fc
多租户更改
2026-08-11 15:59:57 +08:00
richjohnrambo
5aa7733515
chore: sync project files
2026-08-11 10:29:38 +08:00
richjohnrambo