Tiny Core Extensions > TCE 1.x

apache2.tce

<< < (2/3) > >>

Jason W:
I started apache as a .tce and here is what I saw: hence the adding of the .tcel:

httpd: error while loading shared libraries: libaprutil-1.so.0: cannot open shared object file: No such file or directory

No big deal.

I will rename the extension to apache2.tcel.

EDIT: started with httpd instead of apachectl which was the problem, I am not much of an apache person.

Thanks,
JW

Jason W:
Thanks to softwaregurl for an update to apache2.tce:


--- Code: ---Title:          apache2.tce
Description:    Apache HTTP server
Version:        2.2.11
Author:         Apache Software Foundation
Original-site:  http://www.urlstructure.com/apache/httpd/httpd-2.2.11.tar.bz2
Copying-policy: Apache License, Version 2.0
size:           3.1M
Extension_by:   softwaregurl
Comments:       start with "sudo apachectl -k start" help? apachectl -h
                put site in /home/tc/htdocs/
                test with http://127.0.0.1/
                Documentation in apache2-docs.tce
                put License files in /usr/local/share/doc/apache2/
                build script is apache-build.sh
Change-log:     2008/12/21 Original 2.2.8 http://archive.apache.org/dist/httpd/httpd-2.2.8.tar.bz2
                2008/12/30 updated to version 2.2.11
                           wrote build script
                           updated this file (do instructions help?)
                           renamed to apache2.tce (was apache-2.2.8.tcel)
Current:        2008/12/30

--- End code ---



--- Code: ---Title:          apache2-docs.tce
Description:    Apache HTTP server local documentation
Version:        2.2.11
Author:         Apache Software Foundation
Original-site:  http://www.urlstructure.com/apache/httpd/httpd-2.2.11.tar.bz2
Copying-policy: Apache License, Version 2.0
Size:           2.1M
Extension_by:   softwaregurl
Comments:       search for this line in /usr/local/conf/httpd.conf and uncomment it.
                #Include conf/extra/httpd-manual.conf (remove #)
                ADD TO BACKUP if desired.
                start or restart server (sudo apachectl -k restart)
                http://127.0.0.1/manual
Change-log:     2008/12/21 Original (not released) 2.2.8 http://archive.apache.org/dist/httpd/httpd-2.2.8.tar.bz2
                2008/12/30 updated to version 2.2.11
Current:        2008/12/30

--- End code ---

softwaregurl:
I was wondering if apache2 is PPI compatible.  Everything is in /usr/local/... except the web site which is in /home/tc/htdocs/ and should be in persistent home or backup.  apache2-docs should be as I remember.

Mostly just wondering how compatible is defined for the info file.

mikshaw:
I assume that if the application itself is contained within /usr/local it should be pure for PPI.  I don't know about its possible dependencies (sorry i'm a lighttpd guy, so I haven't looked at it =0)).  Also assuming that the web site is configurable, so the user could put that wherever is desired.

Jason W:


This is a good question as to what is PPI compatible since some some extensions contain files that may be above /usr/local yet they are not essential to the extension's operation or they could be listed in the info file as needing to be backed up.  Pppsetup is one example as it's config files are in /etc though the rest of the extension is in /usr/local.  It was going to be a long battle recreating the script to use /usr/local/etc as the config directory so I sort of gave up and stuck with /etc as the config dir and listed in the info file what to back up.  So it is sort of PPI compatible.  To me it is still kind of a grey area, but I guess for now we should go by the simple and hard rule that nothing is to be above /usr/local/ in the extension itself.

When files just have to be in the base system, like /bin/bash, putting a test in the install script to create a symlink will often work.  Bash is PPI compatible as a result of the startup script symlinking /usr/local/bin/bash to /bin/bash.  I personally avoid putting anything in the home directory as it will overwrite stuff there when someone is using persistent home.  Especially now that we have the USER boot option and there are other users than tc.  I see /home/tc is where the htdocs are and that would not benefit someone who is booting as a different user.  Being multiuser makes it not optimal to place extension files in /home/tc.  If I was using the home directory as the web server directory, in the config I would set the server root to "/home/$USER/htdocs" or "~/htdocs".  Also, I would store the index.html say in /usr/local/example.  Then in the install script put:

[ -e /home/$USER/htdocs ] || mkdir /home/$USER/htdocs && cp /usr/local/example/index.html /home/$USER/htdocs/

That way the extension is PPI compatible and will not overwrite an existing index.html that is in persistent home.

I hope I don't appear critical but rather just trying to help.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version