jablonka.czprosek.czf

weathermap

 Subversion Repositories:
[/] [docs/] [pages/] [install-cli-editor.html] - Diff between revs 1 and 85

Show entire file Ignore whitespace

Rev 1 Rev 85
Line 6... Line 6...
<link rel="stylesheet" type="text/css" media="screen" href="weathermap.css" /> <link rel="stylesheet" type="text/css" media="screen" href="weathermap.css" />
<meta name="generator" content= <meta name="generator" content=
"HTML Tidy for Mac OS X (vers 12 April 2006), see www.w3.org" /> "HTML Tidy for Mac OS X (vers 12 April 2006), see www.w3.org" />
   
<title>PHP Weathermap <title>PHP Weathermap
v0.91 v0.97a
- Installation - Command-Line Tool and Editor</title> - Installation - Command-Line Tool and Editor</title>
<style type="text/css" media="print"> <style type="text/css" media="print">
/*<![CDATA[*/ /*<![CDATA[*/
body { font-size: 12pt; } body { font-size: 12pt; }
a { color: black; text-decoration: underline; font-weight: normal;} a { color: black; text-decoration: underline; font-weight: normal;}
Line 39... Line 39...
</ul> </ul>
</div> </div>
   
<div id="header"> <div id="header">
<h1>PHP Weathermap <h1>PHP Weathermap
v0.91 v0.97a
</h1> </h1>
<h4>Copyright &copy; 2005-2007 Howard Jones, <tt><a <h4>Copyright &copy; 2005-2010 Howard Jones, <tt><a
href="mailto:howie@thingy.com">howie@thingy.com</a></tt>. (<a href="mailto:howie@thingy.com">howie@thingy.com</a></tt>. (<a
href="http://www.network-weathermap.com/">Website</a>)</h4> href="http://www.network-weathermap.com/">Website</a>)</h4>
</div> </div>
   
   
<h2>Installation</h2> <h2>Installation</h2>
<h3>Command-Line Tool and Editor</h3> <h3>Command-Line Tool and Editor</h3>
   
<h4>Requirements</h4> <h4>Requirements</h4>
<p>You will need the 'pcre' and 'gd' PHP modules in <em>both your command-line and server-side (mod_php/ISAPI) PHP</em>. The command-line tool runs using the command-line PHP, and the editor uses the server-side one. In some situations it is possible to have two completely different PHP installations serving these two - if you install from a package, then re-install from source, but to a different directory, for example. The editor and the CLI tool should both warn you if the part they need is not present.</p>> <p>You will need the 'pcre' and 'gd' PHP modules in <em>both your command-line and server-side (mod_php/ISAPI) PHP</em>. The command-line tool runs using the command-line PHP, and the editor uses the server-side one. In some situations it is possible to have two completely different PHP installations serving these two - if you install from a package, then re-install from source, but to a different directory, for example. The editor and the CLI tool should both warn you if the part they need is not present.</p>>
  <p>The command-line tool uses the Console_Getopt <a href="http://pear.php.net/">PEAR</a> module. This comes as standard with PEAR, so you should be able to just install PEAR to get it. This may be a seperate package/port/RPM on your system, or you may need to install it from pear.php.net</p>
<p>Before you start using it, you might want to change one PHP setting. Weathermap uses a fair bit of memory by PHP standards, as it builds the image for the map in memory before saving it. As a result, your PHP process <i>may</i> run out of memory. PHP has a 'safety valve' built-in, to stop runaway scripts from killing your server, which defaults to 8MB in most versions (this has changed in 5.2.x). This is controlled by the 'memory_limit =' line in php.ini. You may need to increase this to 32MB or even more if you have problems. These problems will typically show up as the process just dying with no warning or error message, as PHP kills the script.</p> <p>Before you start using it, you might want to change one PHP setting. Weathermap uses a fair bit of memory by PHP standards, as it builds the image for the map in memory before saving it. As a result, your PHP process <i>may</i> run out of memory. PHP has a 'safety valve' built-in, to stop runaway scripts from killing your server, which defaults to 8MB in most versions (this has changed in 5.2.x). This is controlled by the 'memory_limit =' line in php.ini. You may need to increase this to 32MB or even more if you have problems. These problems will typically show up as the process just dying with no warning or error message, as PHP kills the script.</p>
   
<h4>Installation</h4> <h4>Installation</h4>
   
<p>Unpack the zip file into a directory somewhere. If you are intending to use the browser-based editor, then the directory that you unpack the zip file into should be within the 'web space' on the web server that runs your data-collection application (that is, Cacti, MRTG, or similar) - /var/www/html, /usr/local/www/data or whatever it is for you.</p> <p>Unpack the zip file into a directory somewhere. If you are intending to use the browser-based editor, then the directory that you unpack the zip file into should be within the 'web space' on the web server that runs your data-collection application (that is, Cacti, MRTG, or similar) - /var/www/html, /usr/local/www/data or whatever it is for you.</p>
Line 96... Line 97...
</div> </div>
   
In a pinch, you can just <tt>chmod 777 configs</tt>, but this <em>really isn't</em> a recommended solution for a production system.</p> In a pinch, you can just <tt>chmod 777 configs</tt>, but this <em>really isn't</em> a recommended solution for a production system.</p>
<p>On Windows, the same applies - the user that runs the webserver runs as should have permissions to write new files, and change existing files in the configs folder.</p> <p>On Windows, the same applies - the user that runs the webserver runs as should have permissions to write new files, and change existing files in the configs folder.</p>
</p> </p>
   
  <p>Since version 0.97, you now also need to enable the editor. The reason is so that you can't have the editor enabled without
  knowing about it. The editor allows access to your config files without authentication, so you should consider using
  features in your webserver to limit who can access <tt>editor.php</tt>. For example, on an Apache server, something like:
  <pre>
  &lt;Directory /var/www/html/weathermap&gt;
  &lt;Files editor.php&gt;
  Order Deny,Allow
  Deny from all
  Allow from 127.0.0.1
  &lt;/Files&gt;
  &lt;/Directory&gt;
  </pre>
  When you are happy that the world can't edit your maps, then enable the editor. This is done by editing the top of editor.php and changing <code>$ENABLED=false;</code> to <code>$ENABLED=true;</code></p>
   
   
<p> <p>
You should now be able to go to http://yourserver/wherever-you-unpacked-weathermap/editor.php in a browser, and get a welcome page that offers to load or create a config file. That's it. All done. Please see the <a href="editor.html">editor manual page</a> for more about <i>using</i> the editor! You should now be able to go to http://yourserver/wherever-you-unpacked-weathermap/editor.php in a browser, and get a welcome page that offers to load or create a config file. That's it. All done. Please see the <a href="editor.html">editor manual page</a> for more about <i>using</i> the editor!
</p> </p>
<p> <p>
<strong>Important Security Note:</strong> The editor allows <i>anyone</i> who can access editor.php to change the configuration files for your network weathermaps. There is no authentication built-in for editing, even with the Cacti Plugin. This is why the configuration file doesn't exist by default - the editor won't work until you choose to make it work. It's recommended that you either: <ul><li>change the ownership of configuration files so that the editor can't write to them once they are complete, or </li><li>use your webserver's authentication and access control facilities to limit who can access the editor.php URL. On apache, this can be done using the FilesMatch directive and mod_access.</li></ul> <strong>Important Security Note:</strong> The editor allows <i>anyone</i> who can access editor.php to change the configuration files for your network weathermaps. There is no authentication built-in for editing, even with the Cacti Plugin. This is why the configuration file doesn't exist by default - the editor won't work until you choose to make it work. It's recommended that you either: <ul><li>change the ownership of configuration files so that the editor can't write to them once they are complete, or </li><li>use your webserver's authentication and access control facilities to limit who can access the editor.php URL. On apache, this can be done using the FilesMatch directive and mod_access.</li></ul>

Powered by WebSVN 2.2.1