-
Notifications
You must be signed in to change notification settings - Fork 922
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
flower-via-docker-compose example #2626
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @NikosVlachakis,
This is great :)
I left some comments below. In this first review i mostly focused on following the steps in the readme to run the code. The grafana
dashboard is not populated with charts automatically. I believe the uid
needs to be fixed both in the dashboard .json
and the prometheus
& grafana
configs.
It would be ideal if could add a couple of links to some resources (maybe a grafana tutorial in their docs) so people running the example can look into the reference material in case they want to expand how the dashboard looks like or learn more about grafana. Having links to prometheus
and cadvisor
docs is also good.
I like how the docker compose file is generated.
examples/flower-via-docker-compose /config/provisioning/dashboards/default_dashboard.json
Outdated
Show resolved
Hide resolved
examples/flower-via-docker-compose /config/provisioning/datasources/prometheus-datasource.yml
Outdated
Show resolved
Hide resolved
examples/flower-via-docker-compose /helpers/generate_docker_compose.py
Outdated
Show resolved
Hide resolved
… an argument to the client.oy command
@Robert-Steiner, please take a look at this example when you have some time. It looks completed to me eyes. But maybe you have some suggestions regarding how docker/docker-compose (or even grafana/prometheus) that we should incorporate to make this example more future proof. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@NikosVlachakis, this looks great!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great PR, looking forward to merging this soon!
Just one small detail: for the images in public
, could we remove them and link them similar to how we do it with the Flower logo?
Hey Daniel, thank you. |
Yes, exactly. When we link to images, we don't need to commit them to the repo, and it's clear where they come from for users. |
Head branch was pushed to by a user without write access
Ok, I see, I removed the public folder and created publicly available urls for each image. |
Issue
Description
Related issues/PRs
Proposal
Explanation
Checklist
#contributions
)Any other comments?