Skip to content
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

Dashboard overview of multi-bots instances #11

Closed
gaugau3000 opened this issue Jun 4, 2020 · 2 comments · Fixed by #478
Closed

Dashboard overview of multi-bots instances #11

gaugau3000 opened this issue Jun 4, 2020 · 2 comments · Fixed by #478
Labels
enhancement New feature or request

Comments

@gaugau3000
Copy link
Member

As a trader,
I want to have a dashboard that gather and show statistics of all running bots (equity curve, profit...)
So that I make a global analysis and see correlations between their results.

@xmatthias
Copy link
Member

xmatthias commented Jun 4, 2020

I don't see a dashboard connecting to multiple bots as in scope for this project at the moment.

It'll be a control UI for one bot - but you can obviously run multiple bots (with different ports) - and connect to each of them separately.

Since the goal is to deploy this via the flask-api server of freqtrade - you can then enable it and go to localhost:8080/ui (or something like this) - and get to the UI of this bot.

Connecting from one url to different URL's api's has some security implications which need to be very well considered ... so if you don't mind, i'd keep this out of scope for now completely.

It is a possibility for the far far future (when everything else works as it should and looks as it should) to support connecting to multiple bots (and switching bots - similar to cointracking.info) - but it's something that can be added at a later point - but for now, the focus is clearly not this part.

Keep in mind - we now have no UI whatsoever.

@xmatthias xmatthias added enhancement New feature or request Out of Scope Currently out of scope - can be revisited later labels Jun 4, 2020
@xmatthias
Copy link
Member

I've now created an "out of scope" label - which we can add to issues like this - which will allow us to keep the issues clean, but easily return to requests later (hope this makes sense?)

@xmatthias xmatthias mentioned this issue Sep 5, 2021
11 tasks
@xmatthias xmatthias removed the Out of Scope Currently out of scope - can be revisited later label Sep 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants