I'm curious as to the reason that Spar seems to flatten the directory structure of my html files when deploying to S3.
If I've got a directory of view files set up like so
views/
- pages/
-- home.html.haml
-- about.html.haml
-- contact.html.haml
When using the S3 deployment strategy it converts what I would expect to be views/pages/home.html to views/pages/home/index.html
My guess is that this is essentially handling "rewrite" type functionality for "pretty urls". Unfortunately my application is actually looking for those files in the structure that I placed them. Is there some sort of convention here that I should be aware of? I'd love to have a configuration option if there isn't one and would be more than happy to do a pull request if it helps.
Just wanted to see if I was missing something bigger.
Regardless, thanks for Spar! It's pretty killer and scratches one of the itches I had for single page application development.
I'm curious as to the reason that Spar seems to flatten the directory structure of my html files when deploying to S3.
If I've got a directory of view files set up like so
When using the S3 deployment strategy it converts what I would expect to be
views/pages/home.htmltoviews/pages/home/index.htmlMy guess is that this is essentially handling "rewrite" type functionality for "pretty urls". Unfortunately my application is actually looking for those files in the structure that I placed them. Is there some sort of convention here that I should be aware of? I'd love to have a configuration option if there isn't one and would be more than happy to do a pull request if it helps.
Just wanted to see if I was missing something bigger.
Regardless, thanks for Spar! It's pretty killer and scratches one of the itches I had for single page application development.