This project is read-only.

application folder in root of orchard

Topics: General
Oct 4, 2012 at 1:28 AM
Edited Oct 4, 2012 at 1:33 AM

I have an orchard site; I also have a small php web site that lives completely within a folder within orchard.

What's the best practice for me to tell orchard to ignore anything in the "/someothersite" folder?

Maybe place it in another folder outside of the orchard directly and create an application under orchard in IIS that points to this other folder? Or is there something in the web.config that I may configure to essentially let the user browse that folder?

I assume the first option is correct; just not sure on best practice since I can't get both sites in orchard in enough time.

btw: when I do this; I still get the 404 (due to the orchard web.config) - I assumed that I'd get lucky and not have to unrestrict this.  When I remove those settings completely all kinds of problems happen; but in either case - I'd like to only add an exception for this "/someothersite" - has anyone done something like this?


Oct 10, 2012 at 5:44 AM