allow access to other files and CGIs on the server
Idea
allow access to other files and CGIs on the server+issues
If someone wants to shift their site over to Wagn but has existing applications that cannot be handles by Wagn (or files that could be Wagn'd but that they don't want to have to move to make the shift), then we need to provide a way for Wagn to pass through the relevant URLs.
allow access to other files and CGIs on the server+solution
Anything in a folder has a slash in the URL. Since we disallow slashes in card names, those could just be passed through.
This does not handle URLs of the form wagn.org/foo (say foo is a CGI doing something that Wagn doesn't yet). To handle this we could add a pass-through setting, so if "foo+*self+*pass-through" is yes (it's a Toggle), then Wagn would let wagn.org/foo be handled by the web server. (To edit the foo card you'd have to use wagn.org/card/edit/foo )
When we replace plusses with slashes, the pass-through setting could be expanded - instead of being a Toggle it can be "file" or "folder". If foo is set to be a folder, then URLs like wagn.org/foo/app and wagn.org/foo/deep/folders/app all work.
To enable Wagn content to be accessed via URLs 'inside' such folders we could implement the file/folder distinction (even before cardnames can have slashes) and then add a *folder setting, such that if "diamond+*self+*folder" Points to "emerald" (and emerald is a *pass-through folder), then wagn.org/emerald/foo is passed through, but wagn.org/emerald/diamond returns the Wagn card "diamond".
allow access to other files and CGIs on the server+discussed in support tickets
allow access to other files and CGIs on the server+relevant user stories