-
Notifications
You must be signed in to change notification settings - Fork 1.2k
dashboards with subfolders #516
Comments
Dashing is really just a Sinatra app under the hood. Here is the route that defines how the dashboards are accessed: Lines 78 to 86 in f4b121e
In your |
Ah, alright, thank you, I'll play with the routes and see if I can get it to do all subfolders, recursively. |
You can probably just use wildcard routes like |
Any update on this? Can this be closed? |
I tried adding the suggestion to the config.ru and editing the app.rb file, but all it seems to do is add a folder path to the URL, and screw up the data so the data is no longer showing for the widgets. I do not know anything about sinatra, and Ruby is still pretty foreign to me as well. The page used to be served like this: site:3030/simple Seems like it just added folders to the URL, but thats it. Also, it destroyed the Data. |
Sorry I edited dashing.rb apparently. However, trying app.rb (Which is in a different gem sub folder for ruby), doesn't seem to work either. There are 2 folders: |
I have a PR open at the moment which supports this. See #306 and add a +1 for a merge if you like it :) |
Your issue with no data might be the same as mine: the request to the event source needs a leading / on it. Check the PR to see where it goes. |
I tried y our code Floppy and can get it most of the way working. However, it says "Drats!...." inside each widget. Indicating that even though it is correctly parsing the subdirectories, its somehow not correctly rendering the widgets. |
simply creating sub folders under ../dashboards/ then adding .erb files does not allow them to be viewed on the site
http://myfancyserver.com/subfolder/board.erb
What file do I need to modify or play with so that dashing will look at sub folders in the dashboards directory?
EDIT for Clarification:
There will be MULTIPLE dashboards and sub folders.
An imaginary structure might be:
Each of which might have its own dashboad with multiple widgets on them.
The text was updated successfully, but these errors were encountered: