docker setup: docker compose without testing app #5839
Conversation
|
Welcome to the SigNoz community! Thank you for your first pull request and making this project better. 🤗 |
|
|
|
Hi @szobov, |
|
Hey @grandwizard28 |
szobov
force-pushed
the
docker-compose-without-testing-app
branch
from
13627b1
to
fc19f35
Compare
grandwizard28
had a problem deploying
to
testing
GitHub Actions
Failure
|
Hey @szobov, You can proceed with updating the documentation here: https://signoz.io/docs/operate/docker-standalone/#remove-the-sample-application-from-signoz-dashboard |
Application from SigNoz Dashboard" section The new section is "Running SigNoz without Sample Application". It reflects changes made in SigNoz/signoz#5839
|
Hey @grandwizard28 Thanks for the heads up! |
|
Congrats on merging your first pull request! |
) Application from SigNoz Dashboard" section The new section is "Running SigNoz without Sample Application". It reflects changes made in SigNoz/signoz#5839
Summary
Hey there,
Thanks for making such an excellent self-hosted traceability platform! 💪
I wanted to adopt SigNoz, but I faced an issue because I needed to use a vendor docker-compose file when I didn't need a test application.
Current documentation proposes commenting out these services in
docker-compose.yaml.Since docker-compose supports
includecommand, we can overcome the need to edit existing code and also remove code duplication 🔪I preserved the existing interfaces, so:
docker compose -f docker/clickhouse-setup/docker-compose.yaml up -d, would run the same set of services (with the testing app).The interface that was added is:
docker compose -f docker/clickhouse-setup/docker-compose-minimal.yaml up -d, which won't run testing app.Please let me know if you like it, and then I can update the documentation.
I'm looking forward to your comments!