#general

Best Practices to Version Signoz Config Files

TLDR Angeles asks about best practices for versioning Signoz config files. Prashant suggests checking out release branches or tags and examining components in docker-compose.yaml.

Powered by Struct AI
raised_hands1
5
4mo
Solved
Join the chat
May 03, 2023 (4 months ago)
Angeles
Photo of md5-ec364b3d79920c6c343aba9ccd6f4952
Angeles
12:36 PM
Hello guys, curious question, which are the best practices to version Signoz config files? Is better to clone all Signoz application repository and then pushed to my private repo ? or just keep and git the deploy/ folder ?
vishal-signoz
Photo of md5-f936d3e5743d23344d6c60813189716f
vishal-signoz
12:51 PM
Prashant Will be best person to answer this
Prashant
Photo of md5-1899629483c7ab1dccfbee6cc2f637b9
Prashant
04:04 PM
Hello Angeles 👋

You can git checkout to release branch or tags and observe the version of the components in docker-compose.yaml: signoz (frontend, query-service), signoz alertmanager, signoz otel-collector, clickhouse, and zookeeper.
raised_hands1
04:05
Prashant
04:05 PM
release branch will look like release/v0.18.2 while the tag will look like v0.18.2
May 04, 2023 (4 months ago)
Angeles
Photo of md5-ec364b3d79920c6c343aba9ccd6f4952
Angeles
12:33 PM
Thanks a lot for the infos !