HTML-WebMake
view release on metacpan or search on metacpan
doc/allinone.html view on Meta::CPAN
</pre>
</p>
<p>
And edit the <code><a href="cgistart.html">webmake.cgi</a></code> script, changing the value for
<strong>$FILE_BASE</strong>. Only files and sites below this directory will be
editable.
</p>
<p>
Note that <code><a href="cgistart.html">webmake.cgi</a></code> runs with the web server's username and password,
so you may have to <code>chown</code> or <code>chmod</code> files for it to work.
</p>
<a name="Supporting_Metadata_On_Media"><h1>Supporting Metadata On Media</h1></a><p>
If you attach <a href="metadata.html">metadata</a> (e.g. titles) to images or other media items using
<code><a href="cgistart.html">webmake.cgi</a></code>, it will write that <a href="metadata.html">metadata</a> to a file called <code><a href="metadata.html">metadata</a>.xml</code>
in the top-level directory of the site. To pick this up, you will need to add
the following <<a href="metatable.html">metatable</a>> directive to your site:
</p>
<p>
doc/allinone.html view on Meta::CPAN
Any machines you plan to run <a href="cgistart.html">webmake.cgi</a> on, you will also need to generate a
key-pair for, so that the user the web server runs CGI scripts as will be able
to communicate without passwords. Here's how (run these as root):
</p>
<p>
<pre><!--etsafe-->
mkdir ~apache/.ssh
chmod 700 ~apache/.ssh
chown apache ~apache/.ssh
su apache -s/bin/sh -c 'ssh-keygen -P "" -N ""'
<!--/etsafe-->
</pre>
</p>
<p>
This will generate a public/private key-pair for the web server user. Note
that the user the web server runs as on your UNIX may be different (<strong>httpd</strong>,
<strong>www</strong>, or <strong>nobody</strong> are common usernames for it); in that case replace
<strong>apache</strong> with the correct username.
doc/allinone.html view on Meta::CPAN
<!--/etsafe-->
</pre>
</p>
<p>
then, as root,
</p>
<p>
<pre><!--etsafe-->
chown -R apache /var/www/html/jmason.org
<!--/etsafe-->
</pre>
</p>
<p>
so that <a href="cgistart.html">webmake.cgi</a> can read and write the files. (You could also chgrp them
to <strong>www</strong> or whatever the web server user uses as its gid, and <strong>chmod -R
g+w</strong> them.)
</p>
<p>
doc/cgiinstall.html view on Meta::CPAN
</pre>
</p>
<p>
And edit the <code><a href="cgistart.html">webmake.cgi</a></code> script, changing the value for
<strong>$FILE_BASE</strong>. Only files and sites below this directory will be
editable.
</p>
<p>
Note that <code><a href="cgistart.html">webmake.cgi</a></code> runs with the web server's username and password,
so you may have to <code>chown</code> or <code>chmod</code> files for it to work.
</p>
<a name="Supporting_Metadata_On_Media"><h1>Supporting Metadata On Media</h1></a><p>
If you attach <a href="metadata.html">metadata</a> (e.g. titles) to images or other media items using
<code><a href="cgistart.html">webmake.cgi</a></code>, it will write that <a href="metadata.html">metadata</a> to a file called <code><a href="metadata.html">metadata</a>.xml</code>
in the top-level directory of the site. To pick this up, you will need to add
the following <<a href="metatable.html">metatable</a>> directive to your site:
</p>
<p>
doc/cgiinstall.txt view on Meta::CPAN
New password: <em>(type a password here)</em>
Re-type new password: <em>(again)</em>
Adding password for user jm
</pre>
And edit the ##webmake.cgi## script, changing the value for
**&wmdollar;FILE_BASE**. Only files and sites below this directory will be
editable.
Note that ##webmake.cgi## runs with the web server's username and password,
so you may have to ##chown## or ##chmod## files for it to work.
Supporting Metadata On Media
----------------------------
If you attach metadata (e.g. titles) to images or other media items using
##webmake.cgi##, it will write that metadata to a file called ##metadata.xml##
in the top-level directory of the site. To pick this up, you will need to add
the following <metatable> directive to your site:
<safe>
doc/cvshowto.html view on Meta::CPAN
key-pair for, so that the user the web server runs CGI scripts as will be able
to communicate without passwords. Here's how (run these as root):
</p>
<p>
<pre>
<!--etsafe-->
mkdir ~apache/.ssh
chmod 700 ~apache/.ssh
chown apache ~apache/.ssh
su apache -s/bin/sh -c 'ssh-keygen -P "" -N ""'
<!--/etsafe-->
</pre>
</p>
<p>
This will generate a public/private key-pair for the web server user. Note
that the user the web server runs as on your UNIX may be different (<strong>httpd</strong>,
<strong>www</strong>, or <strong>nobody</strong> are common usernames for it); in that case replace
<strong>apache</strong> with the correct username.
doc/cvshowto.html view on Meta::CPAN
</pre>
</p>
<p>
then, as root,
</p>
<p>
<pre>
<!--etsafe-->
chown -R apache /var/www/html/jmason.org
<!--/etsafe-->
</pre>
</p>
<p>
so that <a href="cgistart.html">webmake.cgi</a> can read and write the files. (You could also chgrp them
to <strong>www</strong> or whatever the web server user uses as its gid, and <strong>chmod -R
g+w</strong> them.)
</p>
<p>
doc/cvshowto.txt view on Meta::CPAN
When it asks for the filenames to save the keys in, hit Enter to accept the
defaults.
Any machines you plan to run webmake.cgi on, you will also need to generate a
key-pair for, so that the user the web server runs CGI scripts as will be able
to communicate without passwords. Here's how (run these as root):
<safe>
mkdir ~apache/.ssh
chmod 700 ~apache/.ssh
chown apache ~apache/.ssh
su apache -s/bin/sh -c 'ssh-keygen -P "" -N ""'
</safe>
This will generate a public/private key-pair for the web server user. Note
that the user the web server runs as on your UNIX may be different (**httpd**,
**www**, or **nobody** are common usernames for it); in that case replace
**apache** with the correct username.
Don't worry; the keys you've set up will not compromise your server's
security, as the SSH daemon will not allow anyone to log in as the web server
doc/cvshowto.txt view on Meta::CPAN
(**jmason.org** in the example above). We don't want that, so move them
nearer:
<safe>
mv jmason.org/* . ; rmdir jmason.org
</safe>
then, as root,
<safe>
chown -R apache /var/www/html/jmason.org
</safe>
so that webmake.cgi can read and write the files. (You could also chgrp them
to **www** or whatever the web server user uses as its gid, and **chmod -R
g+w** them.)
Next, copy the ''webmake.cgi'' script to your web server's cgi-bin directory:
<safe>
cp webmake.cgi /cgi-bin/editsite.cgi
( run in 3.255 seconds using v1.01-cache-2.11-cpan-71847e10f99 )