SliTaz Repositories

     1.1 --- a/doc/cookutils.en.html	Fri May 27 19:18:56 2011 +0100
     1.2 +++ b/doc/cookutils.en.html	Tue Jun 07 12:06:02 2011 +0200
     1.3 @@ -30,6 +30,10 @@
     1.4  	use the same DB files and wok, they both share <a href="#blocked">blocked</a>
     1.5  	and broken packages as well as any activity.
     1.6  </p>
     1.7 +<p>
     1.8 +	For some technical informations, the coding style, please refer to the
     1.9 +	README in source tree or: /usr/share/doc/cookutils
    1.10 +</p>
    1.11  
    1.12  <h3>Cook usage</h3>
    1.13  <p>
    1.14 @@ -294,10 +298,10 @@
    1.15  <p>
    1.16  	To let you view log files in a nice way, keep trace of activity and help find
    1.17  	errors, you can use the Cooker Web interface located by default in the folder
    1.18 -	/var/www/cgi-bin/cooker. If you don't use a chroot and the Busybox httpd
    1.19 -	web server is running, the web interface will work without configuration and
    1.20 -	should be reachable at: <a href="http://localhost/cgi-bin/cooker/cooker.cgi">
    1.21 -		http://localhost/cgi-bin/cooker/cooker.cgi</a> 
    1.22 +	/var/www/cooker. If you don't use a chroot and the Busybox httpd web server
    1.23 +	is running, the web interface will work without configuration and should be
    1.24 +	reachable at: <a href="http://localhost/cooker/cooker.cgi">
    1.25 +		http://localhost/cooker/cooker.cgi</a> 
    1.26  </p>
    1.27  <p>
    1.28  	If you used a chroot environment, you should also install cookutils on your
    1.29 @@ -315,10 +319,11 @@
    1.30  </pre>
    1.31  <p>
    1.32  	Note: It's not obligatory to install the cookutils on your host to use the
    1.33 -	web interface, you can also copy the cooker.cgi and style.css files for
    1.34 -	example into your ~/Public directory and use a custom cook.conf with it. The
    1.35 -	advantage of installing cookutils on the host is to get regular updates via
    1.36 -	the Tazpkg packages manager. Say you have cloned or downloaded the cookutils:
    1.37 +	web interface. If you use Lighttpd you can also copy the cooker.cgi and
    1.38 +	style.css files for example into your ~/Public directory and use a custom
    1.39 +	cook.conf with it. The advantage of installing cookutils on the host is to
    1.40 +	get regular updates via the Tazpkg packages manager. Say you have cloned or
    1.41 +	downloaded the cookutils:
    1.42  </p>
    1.43  <pre>
    1.44  $ cp -a cookutils/web ~/Public/cgi-bin/cooker