t94j0
Reconsider a few defaults
We've been using satellite for a bit now, and there are a couple of observations that we have after using the tool, that we wanted to provide as feedback and potential features/changes:
Default Serve Perhaps you have another use case, but in our usage, it seems plausible to default to serving a file/route, even in the absence of a .info file. In this case, test.html for example, will always be served. Standard route configuration can be optionally applied if a test.html.info exists. Perhaps there could be a configuration directive to specifically not serve the file in this configuration. While it's easy enough to create the .info files in the current incarnation, it makes it slightly more difficult to quickly identify the key files that have configurations beyond being just served.
Default mime-types: It would be useful to have a site-wide list of default mime-types for common file extensions that apply if they're not overridden in the .info file. For example, currently *.css files get transferred with a mime-type of text/html which breaks processing (at least in chrome). If you're using a copied site, it quickly gets cumbersome to add that to each css.info file.
