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`.
vishal-signoz
Wed, 03 May 2023 12:51:23 UTCPrashant Will be best person to answer this
Prashant
Wed, 03 May 2023 16:04:37 UTCHello Angeles :wave: 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.
Prashant
Wed, 03 May 2023 16:05:01 UTCrelease branch will look like `release/v0.18.2` while the tag will look like `v0.18.2`
Angeles
Thu, 04 May 2023 12:33:06 UTCThanks a lot for the infos !
SigNoz Community
Indexed 1061 threads
Built with ClickHouse as datastore, SigNoz is an open-source APM to help you find issues in your deployed applications & solve them quickly | Knowledge Base powered by Struct.AI
View in App
Angeles
Wed, 03 May 2023 12:36:32 UTCHello 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 *?*