On Fri, 2007-05-25 at 17:07 +0200, Tijnema wrote: > On 5/25/07, Edward Kay <edward@xxxxxxxxxx> wrote: > > > > > -----Original Message----- > > > From: Tijnema [mailto:tijnema@xxxxxxxxx] > > > > > > > > > > It's just the way you write script, my included files contain only > > > > > functions & variables, no executing code. 99% I have a class around > > > > > it. > > > > > If you write it like that, than there's no problem with execution the > > > > > included file directly, as it loads the class but doesn't do anything > > > > > with it :) > > > > > > > > > > Tijnema > > > > > > > > > > > > > Why are your include files in your web root in the first place? > > > Move them > > > > elsewhere on your filesystem and then it's not even possible to > > > access them > > > > via the web. > > > > > > > > Edward > > > > > > > Oh, I don't want my web files all over the filesystem, I want to keep > > > all files for a single project inside a single folder on my webserver. > > > So, that if i move them around, I have all files there. > > > > > > Tijnema > > > > This is exactly what I do - one folder per project. You just have you > > web-root as a sub folder in this, eg: > > > > /project > > /includes <- nicely protected > > /public_html <- web root > > /images > > index.php > > ... > > ... > > > > Edward > > > Hmm, way too complicated :P > > I like to keep it simple, just like this: > / > /data > /http > /project1 > /includes > config.php << With passwords :P > /images > /project2 > /includes You won't like mine then :) /wherever /Project /bin /build /source /static /templates patterns.txt /compilers /configs /cron /functions /modules /services /sql buildSite.php* config.interjinn.php@ (link to active config in /configs) Running buildSite.php (which uses patterns.txt) generates the webtree: /wherever /DOC_ROOT Cheers, Rob. -- .------------------------------------------------------------. | InterJinn Application Framework - http://www.interjinn.com | :------------------------------------------------------------: | An application and templating framework for PHP. Boasting | | a powerful, scalable system for accessing system services | | such as forms, properties, sessions, and caches. InterJinn | | also provides an extremely flexible architecture for | | creating re-usable components quickly and easily. | `------------------------------------------------------------' -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
