Open nathanbowser opened 10 years ago
Sorry for bumping an old issue, but this is still a "problem"/something that would be nice. Attached a screenshot where you can see the problem.
(and don't please judge me by that youtube tab!)
Definitely looks like a bug. I'll get to this when I can.
Thanks! I "solved" this temporary by setting the url to url: "/sensu/***" in the .coffe-files for each failing part.
root@monitor:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-dashboard-0.10.4/lib/sensu-dashboard/assets# grep -R '/sensu/' *
javascripts/bootstrapper.coffee: url: "/sensu/all" javascripts/models/info.coffee: url: "/sensu/info" javascripts/collections/clients.coffee: url: "/sensu/clients" javascripts/collections/checks.coffee: url: "/sensu/checks" javascripts/collections/stashes.coffee: url: "/sensu/stashes" javascripts/collections/events.coffee: url: "/sensu/events"
Hi,
any updates for this...?
@iiro I'm currently doing a bit of restructuring of the dashboard including converting everything to static HTML files that speak directly to the Sensu API. Once I'm done this issue should no longer be a problem.
It would be nice if the dashboard could be mounted at other locations other than /. It looks like this isn't possible because of https://github.com/sensu/sensu-dashboard/blob/master/lib/sensu-dashboard/assets/javascripts/bootstrapper.coffee#L12 I can mount sensu in a directory (using nginx) of /foo/bar/sensu/, and I see all of the public assets, but the client side xhrs fail because they are trying to access endpoints that don't exist.