-
Notifications
You must be signed in to change notification settings - Fork 269
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
API? #14
Comments
Hi. As I said before this is my first time using Docker in any project so I don't know if it would be possible to implement. Do you know any other project that implements that kind of functionality so I could take a closer look at it? Right now, flame exposes RESTful API for apps, categories and bookmarks if that's what you mean. |
Traefik maybe? I think you need to expose the docker.socket, but I'm no developer, so not sure. |
Sorry, but for now implementation of this feature is out of my skill and knowlage range. |
I'm in a search for such feature, but I guess the popular dashboards options also don't have it. Currently I'm investigating what would be the best option, and I guess Flame seems to be a good candidate (API already there). And instead of trying to consume docker api (like Portainer and Traefik does), I was even thinking about consuming Traefik api (rawdata) -- that way it would be possible to generate apps even for non-docker things, and the whole "url/pathprefix" problem would be already solved. So the problem is divided in different parts, and a final solution could be a mix of any: Data acquisition:
Feature placement:
Target Dashboard:
I've been using Organizr for a few years already, but the other dashboards I installed just recently. |
I'm not sure how much Flame would be able to automatically populate with just labels and nothing else exposed/consumable. If you were to label a container as being flammable, Flame would then need some way of determining the type, category, name, url, and icon for it. Many of those would be awfully hard (if not impossible) to divine on their own, so you'd also need to use labels to define the values. eg:
And at that point, you're pretty much just making a distributed configuration file for Flame. |
Dunno. Maybe you need to connect to the docker socket? The point is to get Flame dynamicly show the active services, so being able to set them that way would be awesome. |
Would it be possible with some sort of API, that you can add labels to your docker-compose files and automatically populate Flames dashboard?
The text was updated successfully, but these errors were encountered: