I cannot get the web server and phpPgAdmin to work…
Using the ‘WebServerKit-zeta.zip’ file, that zip file does not contain any over-arching documentation that details the step-by-step instructions of what to do with these files.
I’m trying to setup RoginHood, but the ‘Installation & Getting Started’ page does not contain any step-by-step instructions such as how to install the package, what config files and their file locations that need respective redactions and so forth. There is no checklist of what to do exactly in proper order and action. Moreover, the documentation telling me how to test and check if it is working properly is lacking.
The page contains a lot of information that is helpful after the web server is up and running–no set-up instructions.
I have Postgres 7.2 & 8.1 working in ZetaOS. Postgresql is very well documented so I have no issues there. I have been using Postgresql in BeOS and Zeta for years (i.e. decades…). In addition, I posted my detailed step-by-step checklist on how to install Postgresql 11 & 12 into Haiku. Refer to PostgreSQL 11.1 Install on H1B1 (64-bit) Notes.
I also unzipped phpPgAdmin and its installation documentation is not very informative–meaning, it has no step-by-step instructions either. I cannot figure out how to get that working either [assuming that the web server is working].
Does anyone have this kind of step-by-step information for RobinHood and phpPgAdmin? Assuming you have worked with these two software.
For Haiku, I also looked at Lighttpd–their documenation also does not contain any step-by-step instructions–so I cannot set it up in Haiku either. Not sure how it works on Haiku’s virtual non-updateable file system partitons–so I can update the config files but they will not persist after the shutdown–that would be bad!
Can Lighttpd be installed into the ‘/boot/home/config/non-packaged’ directory?
[Wish all our software could go into that directory instead where I have full access to ALL files and manage my PC as I see fit! Probably why I still enjoy using Zeta…]
Settings files are (of course) writable and will be saved to disk. They live in /system/settings or /home/config/settings and both directory are perfectly norrmal writable directories. Even better, in the case of lighttpd you don)t even need to put your settings there. Just put the lighttpd.conf file anywhere you want, and give it to the server when you start it: lighttpd -f lighttpd.conf
This also explains why there are no detailed step by step instructions, there are only two steps:
Install the server: pkgman install lighttpd (or lighttpd_x86 if you have a 32bit system)
Run the server: lighttpd -f lighttpd.conf
RobinHood is unmaintained as far as I know, and the README says it was only tested with PHP 4. I don’t know if it will work with later versions.
I like the "no tweaking’ part of this…no updating esoteric parameters and no script/config redactions.
Though looking at TutorialConfiguration - Lighttpd - lighty labs, looks like I need to create a config file for it to run properly. The server.port makes sense; but what does the ‘document root (the base directory that is used for all requests)’ really mean? Is that a working directory for Lighttpd? Do I have to designate it prior to starting Lighttpd or does it have it own default–maybe that is why I cannot get it working.
But, that leads me to my next question: how does one verify that Lighttpd is working as it should? Is there a validation step of some sort?
I would to test the current version of phpPgAdmin in Haiku…but I want to make sure that the web server is operating normal first.
The document root is where your html or php files will be stored. For example if you set document root to /home/www/ and someone goes to yourwebsite.com/somepage.php, lighttpd will load the file from /home/www/somepage.php.
To test everything is working, you can open a web browser (WebPositive for example) and open the page http://localhost/ . Lighttpd should reply to that request and show you something (the index.html from your documentroot if you put one there, or the directory listing if you enabled it, or a 404 error page).
For testing you can run lighttpd -D -f lighttpd.conf in a Terminal. This starts lighttpd as a “foreground” application, meaning all logs are printed to the terminal. So you can see if there are errors in your config file, and once the server is started, you can also see logs for all requests it serves in that terminal.