|
Post by lewinb on Jan 4, 2007 15:57:36 GMT 7
I would like to see a module that leverages iphoto's sharing capabilities, which function identically to the itunes sharing service. Ideally, I should be able to put my iphoto library on the n2100, and specify where it is to the iphoto sharing module. The module would then read the pre-made xml files, thumbs, etc., and serve them, creating minimal work for the processor, and NO file duplication.
Iphoto will share and access shared libraries exactly like itunes, so we should have the option of sharing the iphoto library like a regular iphoto library (ie., just to iphoto clients, over the local network) or to the internet in a web-based format.
I remember a fairly impressive try at this, named myPhoto by Michael Mulligan, which I used for a while but found a but light-weight, because it couldn't use tif files at the time. This brings up another stupid limitation of the built-in photo server: 4 mb per file? Come on! Maybe I'm picky, but this doesn't serve power users or semi-pro photographers very well.
Another very well-executed program of this sort is LinPHa (from sourceforge, if I recall). This unfortunately requires file duplication, and makes NO use of iPhoto's xml library or file structures.
|
|
|
Post by lewinb on Jan 4, 2007 16:36:52 GMT 7
Sorry to reply to myself, but I just did a quick search and found these. they appear to be exactly what I am describing. It doesn't appear to be open-source, but isn't commercial either, exactly. www.bitpatterns.com/iPhotoWebShare/. It apparently has some limitations in working with albums, but is pretty close to what I described. This one looks even better, being released under a free license, and using php: globs.org/articles.php?lng=en&pg=265What are the chances that these (especially the second one) could be modified to work on the n2100?
|
|
|
Post by omega on Jan 4, 2007 17:47:21 GMT 7
Just visited globs.org and found this:
So as I understand, you need Mac OS for this software.... will be difficult for the N2100....
Addition: the same applies to the software iPhotoWebShare (this one is for a MAC too).
Andreas
|
|
|
Post by lewinb on Jan 5, 2007 4:17:29 GMT 7
I downloaded WiPHa from globs.org, and although it says what you quoted, it may not be true. Note the following, from the documentation:
and more specifically,
You're right about the other one though... I was just using it as an example of the features I would like.
So with this in mind, it looks (to me) like using WiPHa on the n2100 should be very possible, since it seems to be just a website that relies on php and plugs into a pre-existing xml database of photos.
|
|
|
Post by omega on Jan 5, 2007 4:59:41 GMT 7
lewinb, I tried to download the WiPHa software and I've received a .dmg file which I cannot convert to an .iso file, because the perl tool dmg2iso tells me the .dmg file is somehow corrupted. Could you send me the software as a .zip or .tar file? Andreas
|
|
|
Post by dbridges on Jan 5, 2007 5:06:06 GMT 7
I can appreciate what your asking because i bought the N2100 to store photos securely. I agree that the gallery is a disappointment because it excludes tif's, has the 4MB limit, allows unsecured public access and runs like a dog because of the 128MB of ram. The file size limit can be easily overcome; i've changed it to 10MB. I've also blocked public access to the gallery and upped the memory to 512MB. N2100:/img/htdocs/gallery# cat GlobalVars.html <? define(AlbumRoot,"/raid/album/"); define(MaxFileSize,4*1024*1024); ?>N2100:/img/htdocs/gallery#
Dont increase the MaxFileSize without increasing the memory. I tried searching for a suitable gallery programs a while back as I would like one with good cataloging capabilities. Unfortunately while there are a lot of Linux/PHP based gallery programs out out there, all of them are reliant on a machine running a full linux distribution with all of it's libraries and/or the ability to run mysql. In then end i went back to managing them by hand. If you find one. Do let me know. Oh and remember... Search for "Linux PHP" galleries
|
|
|
Post by lewinb on Jan 5, 2007 6:08:50 GMT 7
I've received a .dmg file which I cannot convert to an .iso file Are you using a mac? just double-click it, and it will auto-mount. If you're not on a mac, I made a zip archive of the folder that the installer places in the web folder (see below): becky.mine.nu/~becky/wipha.zipI went ahead and installed WiPHa on my mac, and it leads me to further believe that it should be usable on n2100... This is the text output of the installer: Decompacting WiPhA in your Sites folder (/Users/lewinb/Sites)
Setting permissions on these files
Setting setuid bit (lewinb) on permission corrector executable
Grant write access to Apache on the WiPhA data directories
Configuring Apache to handle php
Configuring Apache to take wipha access protection in account (.htaccess)
Checks...
'sips': ok 'data' permission is drwxrwsrwt: ok 'data/cache' permission is drwxrwsrwt: ok 'changeperm' permission is -rwsr-xr-x: ok OSX Standard PHP4 enabled: ok (unless other PHP versions also installed) WiPhA access protection enabled (.htaccess): ok
Installation complete
Re-starting Apache server
|
|
|
Post by omega on Jan 5, 2007 7:26:17 GMT 7
lewinbNo, I'm not using a MAC, but I fetched you zip file, thanks. Indeed it looks like the software only uses JS and PHP. I'll have a look tomorrow - but only for the N5200.... Bye Andreas
|
|
|
Post by dbridges on Jan 5, 2007 9:15:01 GMT 7
lewinbNo, I'm not using a MAC, but I fetched you zip file, thanks. Indeed it looks like the software only uses JS and PHP. I'll have a look tomorrow - but only for the N5200.... Bye Andreas Agreed. The only binary appears to be the changeperm which is just there to set file permissions and a workaround should be available. The rest is PHP and js and even the system execs in php look benign.
|
|
|
Post by lewinb on Jan 8, 2007 9:31:30 GMT 7
Others are probably way ahead of me on this, but I checked for php by putting the script <?php phpinfo() ?> into a document test.php, and putting that in /opt/apache/htdocs/ ...
It came up saying that it's php 5.0.5, and that it was built with the following configuration:
'./configure' '--host=i386-linux' '--target=armv5l-linux' '--prefix=/opt/php' '--with-config-file-path=/opt/apache/conf' '--disable-ipv6' '--with-apxs2=/opt/apache/bin/apxs' '--without-mysql' '--without-pear' '--disable-cli' '--without-jpeg' '--without-iconv' '--enable-sqlite-utf8' '--disable-simplexml' '--disable-dom' '--enable-memory-limit'
I put the wipha site folder there also, but I haven't been able to get anything to come up yet from it. Permissions for the folder are 0755, with owner as root. Should I try setting owner to www?
|
|
|
Post by dbridges on Jan 8, 2007 13:08:41 GMT 7
You'll need to turn on the php messaging on.
There are some symbolic links that get lost along the way which you'll need to create.
I got most of the way but stopped when i ran up against the changeperm binary.
Anyway as a comparison i installed it on the mac and couldn't get it to work fully. What i did see i didn't like so i've given up on the whole thing.
The gallery that's built in is better and it's not dependent on iphoto.
|
|
|
Post by lewinb on Jan 8, 2007 16:16:57 GMT 7
Could you give me a little direction on turning on messaging? I'm not sure what you mean. Is this something I would find in /etc/httpd/conf/php.ini ?
Also, I'm not sure what symlinks you're referring to. I looked through the installation notes from the developer again, and it doesn't mention creating any symlinks. I manually made the changes to httpd.conf that the installer makes (which boiled down to adding the allow from .htaccess comment, since php is already enabled).
I rebooted after I uploaded the new httpd.conf, and I was astonished to find that the entire /opt/apache/htdocs/wipha folder was gone. So I uploaded the entire folder, including the hidden .htaccess file, again, but I still get an error. It doesn't specify what it was, just an "internal server error"
Also, I am getting a bit irritated with all the symlinks in the n2100. For example, even /etc shows up as a symlink. Where the heck IS it?!
|
|
|
Post by dbridges on Jan 8, 2007 17:37:00 GMT 7
Could you give me a little direction on turning on messaging? I'm not sure what you mean. Is this something I would find in /etc/httpd/conf/php.ini ? Also, I'm not sure what symlinks you're referring to. I looked through the installation notes from the developer again, and it doesn't mention creating any symlinks. I manually made the changes to httpd.conf that the installer makes (which boiled down to adding the allow from .htaccess comment, since php is already enabled). I rebooted after I uploaded the new httpd.conf, and I was astonished to find that the entire /opt/apache/htdocs/wipha folder was gone. So I uploaded the entire folder, including the hidden .htaccess file, again, but I still get an error. It doesn't specify what it was, just an "internal server error" Also, I am getting a bit irritated with all the symlinks in the n2100. For example, even /etc shows up as a symlink. Where the heck IS it?! Now we're getting into thecus architecture 101 The symbolic links are primarily because this is a cut down linux distro made to fit on 32MB of flash memory. This is not a lot and the filesystem that you generally see exists on a ram disk. N2100:~# df Filesystem 1k-blocks Used Available Use% Mounted on /dev/ram0 29045 19012 10033 65% / tmpfs 258312 264 258048 0% /var /dev/cloop0 7931 5319 2612 67% /usr/lib /dev/cloop1 3963 448 3515 11% /usr/share/zoneinfo /dev/cloop2 25169 20818 4351 83% /opt /dev/mtdblock3 1152 672 480 58% /app /dev/md0 191296412 26932180 164364232 14% /raid N2100:~#
/dev/md0 is your hard disks /dev/mtdblock3 is the writable component of flash memory /dev/ram0 is the ramdisk The bulk of the filesystem is uncompressed from a tgz file on boot which is why things will get wiped on reboot. Some files hold general configuration info and are kept in /dev/mtdblock3 but need to be found along other paths hence the symbolic links. Over time you'll figure out which ones can be edited and which cant. I actually copied the entire htdocs folder to a /raid/www/htdocs and eddited the httpd.conf to point to the new location. That way all of my web changes stay. I'm presently runnning a couple of sites on different ports. The other alternative is to create an alternate file to the one that you know is going to be overwritten and keep it on the hard disk. You modify the boot script to copy it in place during boot. thecususergroup.proboards106.com/index.cgi?board=modifications&action=display&thread=1155545815Be careful here though always check the execute permission after a change. as for php... /opt/apache/conf/php.ini ; Print out errors (as a part of the output). For production web sites, ; you're strongly encouraged to turn this feature off, and use error logging ; instead (see below). Keeping display_errors enabled on a production web site ; may reveal security information to end users, such as file paths on your Web ; server, your database schema or other information. ; display_errors = On display_errors = Off After you get the errors displaying you'll quickly see what symbolic links are missing. Remember 32MB is not a lot. If you only had 32MB to work with what would you include
|
|
|
Post by lewinb on Jan 9, 2007 11:25:22 GMT 7
grrr... I changed to display_errors = On and display_startup_errors = On and I am still getting nothing but the internal server error message! I restarted apache, and it made no difference. So I enabled error logging, and set it to log to filename = /error_log_php. But, after restarting apache and trying it again, I still get nothing. It didn't write a logfile either. What the heck?! **EDIT: If you don't mind looking at it, I posted my configs here: becky.mine.nu/~becky/test.html
|
|
|
Post by dbridges on Jan 9, 2007 13:01:22 GMT 7
If the php messaging is working then you will see depreciated warnings in the thecus webgui.
Put a simple index.html into the wipha folder and try and access that. If the problem is still occurring then remove the .htaccess file and try again.
Once you can get to the index.html then you can remove it and start on the .php
|
|