pingvinen / localdocs Goto Github PK

The first time a target site is "activated" (per server-run), we should run through the files and do all the checks for custom layouts, config etc. and output a report to the user if something is wrong.

The report output should have a link to re-test the target, so the user wont have to restart the website to see if any changes made fixed the issues.

If you work on multiple projects simultaneously it might be better to be able to reach them using different URLs than having to open the wrong doc and then having to switch the site.

Support for targets without subdomains should continue as IIS does not have support for something like "*.localdocs.local".

It would be a plus if the system could show 2 different targets in the same browser when using subdomains (this should be possible by prepending the subdomain to the session-stuff).

It would be nice to avoid punking the filesystem for every request. This could be achieved by caching the files as they are processed by the handlers.

The caching mechanism needs to be aware of file changes though, as it will otherwise be a nightmare to work on the documentation. Having to remember to turn caching on and off will also be annoying. I am guessing that the FileSystemWatcher should come in handy.

There should also be a time-to-live on each cache entry.

Having a sitemap that contains links to all the files in the doc might be a good fallback.

The default layout is not designed for a specific target site. This means that we have to figure out a way to build usable navigation when we do not know which files are "important".

This is a sub-issue of #2

I like Spark, so try that first.