StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>If you are compiling Apache2 for a particular location but want your clients to be able to install it somewhere else (and I'm assuming they have the same architecture and OS as your build machine) then you can do it but the apachectl script will need some after-market hacking.</p> <p>I just tested these steps:</p> <ol> <li><p>Unpacked the Apache2 source (this should work with Apache 1.3 as well though) and ran <em>./configure --prefix=/opt/apache2</em></p></li> <li><p>Ran <em>make</em> then <em>sudo make install</em> to install on the build machine.</p></li> <li><p>Switch to the install directory (/opt/apache2) and tar and gzip up the binaries and config files. I used <em>cd /opt/apache2; sudo tar cf - apache2 | gzip -c > ~/apache2.tar.gz</em></p></li> <li><p>Move the tar file to the target machine. I decided to install in <em>/opt/mynewdir/dan/apache2</em> to test. So basically, your clients can't use rpm or anything like that -- unless you know how to make that relocatable (I don't :-) ).</p></li> <li><p>Anyway, your client's <em>conf/httpd.conf</em> file will be full of hard-coded absolute paths -- they can just change these to whatever they need. The <em>apachectl</em> script also has hard coded paths. It's just a shell script so you can hack it or give them a <em>sed</em> script to convert the old paths from your build machine to the new path on your clients.</p></li> <li><p>I skipped all that hackery and just ran <em>./bin/httpd -f /opt/mynewdir/dan/conf/httpd.conf</em> :-)</p></li> </ol> <p>Hope that helps. Let us know any error messages you get if it's not working for you.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload