BassKozz

* BassKozz has joined #gallery
<bharat> hello BassKozz
<bharat> I just responded to you in the forums :-)
<BassKozz> cool, Thanks bharat :-D
<BassKozz> got it... So will this setting be added to the install gui in a later beta or final release?
<BassKozz> or will it forever reside solely in the index.php ?
<bharat> dunno.  is there a strong motivation to move it somewhere else?
<BassKozz> Well, my thought is that some people might like to have their gallery storage path as a web inaccesible folder, for example allow it to be set using the install gui as /home/g3data/ instead of /home/domain.com/gallery3/var
<bharat> well, we link directly to the images
<BassKozz> I am not suggesting changing the variable location, just the ability to change the storage path location variable
<bharat> so if you do that, you'll have to do something special to allow the images to be visible
<BassKozz> right, you link directly to the images but someone can't go to the folder where the images are stored directly
<bharat> sorry, you lost me there
<bharat> how would it work if you move var to a location outside of the document root?
<bharat> in that case we'd have to put some kind of proxy in place, right?
<BassKozz> for example, my storage location for my G2 gallery is /home/user/.g2data/ , and my g2 Gallery is /home/user/domain.com/gallery2/
<BassKozz> the gallery pulls the images from the web inaccessible file in /home/user/.g2data/
<bharat> g2 uses a php based proxy for loading images to do that
<BassKozz> ohh, ok, I see g3 doesn't have that ability
<BassKozz> ?
<BassKozz> or should I say doesn't have the proxy in place
<bharat> that proxy is 2-3 *orders of magnitude* slower than direct file access
<BassKozz> roger, speed is a keypoint in G3, and I wouldn't want to see that compromised, so I can live with that.
<bharat> since it's used really heavily, we decided to come up with an alternate mechanism
<bharat> theoretically, you could still move the var dir out, and just leave some symlinks in place to mirror a few key things
<bharat> so that apache could still serve var/{albums,thumbs,resizes} and we could have the code know about the real location
<BassKozz> sounds good to me, I was just curious... What's to stop a user from accessing the /var/ directory directly thou?
<bharat> you can, but the contents of the directory are inaccessible
<BassKozz> for example if you want to keep your images private or for sale or watermarked, how would the user not be able to simply direct their browser to the /var/ directory?
<BassKozz> ohh, ok
<BassKozz> using .htaccess?
<bharat> yup
<BassKozz> cool. Sounds good to me :-P
<bharat> any album that you make inaccessible to guest users
<bharat> gets a .htaccess file that re-routes all users through a proxy
<bharat> so publicly accessible files are *fast*
<bharat> and private files are all transparently forced through an authenticating proxy
<BassKozz> nice, very good.
<BassKozz> Thanks for the explination. Keep up the great work, I can't wait to start using G3 in production.  It's VERY fast (compared to G2). :thumbs-up:
<bharat> thanks!
<BassKozz> Bye 4 now.
<bharat> cya