[Solar-talk] Oddity

Kilbride, James P. James.Kilbride at gd-ais.com
Wed Oct 3 10:33:18 CDT 2007


I assumed that was the case(I shoved a directory in my apache install
called 'SolarConfig' to shove that file into but I'll play around with
it some more at a later date to figure things out. 

It's funny how much more 'comforting' *nix is compared to windows when
it comes to directories and putting things in specific places and then
having to configure where everything is. Btw, I shoved solar into a
directory called Solar-0.28.0 on my C drive then shoved my 'vendor' aka
GDAIS directory into that as well. So I have GDAIS and Solar in the same
directory which is included by the php.ini file. Does this mean, if I'm
reading your documentation correctly, that since it's in the php.ini
file as an include part of the path I don't need to overload the path in
the index.php in my document root?

James Kilbride 

-----Original Message-----
From: solar-talk-bounces at lists.solarphp.com
[mailto:solar-talk-bounces at lists.solarphp.com] On Behalf Of Paul M Jones
Sent: Wednesday, October 03, 2007 11:19 AM
To: solar-talk at lists.solarphp.com
Subject: Re: [Solar-talk] Oddity


On Oct 3, 2007, at 10:53 AM, Kilbride, James P. wrote:

> Okay,
> So in getting started it says, "Although this file may be in the 
> document root, for security reasons it should not be in the document 
> root." but then in the next page it says:
>
> $ cd /home/username/public_html
> $ mate Solar.config.php
> Hold on a second.. the config files in the document root in my public 
> html folder. So which is it? We've turned on rewrite by now so is that

> why it doesn't matter? Except your rewrite rules ignore anything that 
> is really in the directory so it wouldn't ignore that file would it?
>
> Is this just a simple difference of 'opinion'?

The example is for the simplest possible case, and only for example
usage, so that you can call Solar::start() without any params and have
it work (it looks in the webroot for Solar.config.php by default in the
current release).  But you're right, I can see that would be confusing.

The "official line" is to **not** keep configs in the web root.  Have
Solar.config.php somewhere else, and call Solar::start('/path/outside/
webroot/Solar.config.php') to load it.

On the next release, Solar will **not** look in the webroot by default;
you will have to tell it where the config file is (like in the example
above).  At that time I will change the docs to reflect that more
clearly.

Sorry for the confusion, let me know if that helps or not.



--

Paul M. Jones  <http://paul-m-jones.com>

Solar: Simple Object Library and Application Repository for PHP5.
<http://solarphp.com>

Join the Solar community wiki!  <http://solarphp.org>

Savant: The simple, elegant, and powerful solution for templates in PHP.
<http://phpsavant.com>


_______________________________________________
Solar-talk mailing list
Solar-talk at lists.solarphp.com
http://mailman-mail3.webfaction.com/listinfo/solar-talk



More information about the Solar-talk mailing list