WEBGUI EN DEBIAN TIENE SOPORTE
Debian already has WebGUI support
If you want to install WebGUI on a Debian GNU/Linux you can use the readily available packages from Debian's repository. Bear in mind that Debian carries the latest stable WebGUI releases, usually available a day or two after Plainblack's release.
Installation is done using either aptitude from the command line or synaptic from your preferred desktop environment.
Debian Sid (Unstable)
If you are running an up to date Debian Sid (unstable) system, you only need to
aptitude install webgui
in order to get the latest available package installed, including all its dependencies. If you want to have MySQL in the same server, you will need to
aptitude install mysql-server
in order to get it installed.
Debian Lenny (stable)
If you are running an up to date Debian Lenny (stable) sytem, you need to do a few extra things in order to use the WebGUI and YUI packages from Sid, while keeping the rest of your system in Lenny.
Start by adding a proper line to your /etc/apt/sources.list pointing to Sid packages. Keep the lines pointing to Lenny, Debian Security and possibly Debian Volatile unchanged. You should have at least
deb http://http.us.debian.org/debian/ lenny main contrib non-free
deb http://security.debian.org/ lenny/updates main contrib non-free
deb http://http.us.debian.org/debian/ sid main contrib non-free
Note the use of lenny and sid instead of stable and unstable; this prevents unwanted upgrades when newer Debian releases appear.
Then, you will need to configure APT Pinning so your Debian Lenny installation prefers Lenny packages instead of Sid packages, except for the two packages needed for WebGUI: webgui and libjs-yui. This is done by creating or editing /etc/apt/preferences and adding the following stanza
Package: *
Pin: release a=stable
Pin-Priority: 800
Package: webgui, libjs-yui, libclone-perl, libxml-treepp-perl, libxml-feedpp-perl
Pin: release a=unstable
Pin-Priority: 900
Note the use of stable and unstable instead of Lenny and Sid. This has to do with the way pinning works.
Next, update the package lists with the usual
aptitude update
and make sure both Lenny and Sid lists are downloaded.
Finally, install the WebGUI packages doing
aptitude -t sid install webgui
This will pull webgui and libjs-yui from Sid, but the rest of the packages will be pulled from Lenny. There are newer versions for several Perl modules available in Sid, so you might want to add them to your pinning configuration if you're interested in using them, but YMMV.
Database and Apache setup
Check /usr/share/doc/webgui/README.Debian.gz for instructions on database and Apache setup.
Assisted database creation is a work in progress for the Debian package, so in the mean time you'll have to do it manually. The appropiate commands are spelled out for you in README.Debian.
The Debian package cannot assume WebGUI to be the only Apache application, so it provides a couple of sample config files for you to use, and also a couple of Apache modules need to be enabled. Again, the appropiate commands a configuration suggestions are spelled out for you.
The default configuration will have WebGUI running under http://localhost/webgui. If you want to change the root location or have WebGUI take control of the webserver, you'll need to use the alternate configuration file.
WebGUI and the FHS
Debian's WebGUI package strictly follows the FHS, so instead of a /data with everything inside, things are spread out. This means:
* WebGUI libraries are in /usr/share/webgui
* WebGUI log files are in /var/log/webgui, and get rotated automatically thanks to Debian's logrotate configuration.
* WebGUI configuration is in /etc/webgui.
* WebGUI web content is in /var/lib/webgui
* WebGUI utility scripts are in /usr/bin with a wg- prefix, i.e. wg-upgrade instead of plain upgrade.
* Spectre, being a daemon lives in /usr/sbin, and can be handled using /etc/init.d/webgui or through the usual way.
* Every utility script has a proper man page.
* WebGUI will use TinyMCE's as packaged by Debian and not as provided by WebGUI.
* WebGUI will use YUI as packaged by Debian and not as provided by WebGUI.
It also means you cannot start with a Debian package install and then upgrade to a non-Debian package install (WRE or source) unless you know exactly what you are doing.
Indexing and spelling
The Debian package sample WebGUI configuration already has support for PostScript and PDF indexing, so you need not do anything special. Just upload PostScript and PDF files and WebGUI will be able to index them out of the box.
If you want to enable the spell checker, just install as many aspell dictionaries as you want (aspell-en, aspell-es, aspell-de, etc.) and follow the instructions in /usr/share/doc/webgui/README.Debian.gz to enable them.
Bugs? What bugs?
Debian packaging is not done by Plainblack, so if the Debian package is not working for you, something is missing, or you have suggestions in order to improve the packaging, please file a Bug in the Debian BTS or contact the package maintainer (look at /usr/share/doc/webgui/changelog or for SquOnk on IRC).
If you want to install WebGUI on a Debian GNU/Linux you can use the readily available packages from Debian's repository. Bear in mind that Debian carries the latest stable WebGUI releases, usually available a day or two after Plainblack's release.
Installation is done using either aptitude from the command line or synaptic from your preferred desktop environment.
Debian Sid (Unstable)
If you are running an up to date Debian Sid (unstable) system, you only need to
aptitude install webgui
in order to get the latest available package installed, including all its dependencies. If you want to have MySQL in the same server, you will need to
aptitude install mysql-server
in order to get it installed.
Debian Lenny (stable)
If you are running an up to date Debian Lenny (stable) sytem, you need to do a few extra things in order to use the WebGUI and YUI packages from Sid, while keeping the rest of your system in Lenny.
Start by adding a proper line to your /etc/apt/sources.list pointing to Sid packages. Keep the lines pointing to Lenny, Debian Security and possibly Debian Volatile unchanged. You should have at least
deb http://http.us.debian.org/debian/ lenny main contrib non-free
deb http://security.debian.org/ lenny/updates main contrib non-free
deb http://http.us.debian.org/debian/ sid main contrib non-free
Note the use of lenny and sid instead of stable and unstable; this prevents unwanted upgrades when newer Debian releases appear.
Then, you will need to configure APT Pinning so your Debian Lenny installation prefers Lenny packages instead of Sid packages, except for the two packages needed for WebGUI: webgui and libjs-yui. This is done by creating or editing /etc/apt/preferences and adding the following stanza
Package: *
Pin: release a=stable
Pin-Priority: 800
Package: webgui, libjs-yui, libclone-perl, libxml-treepp-perl, libxml-feedpp-perl
Pin: release a=unstable
Pin-Priority: 900
Note the use of stable and unstable instead of Lenny and Sid. This has to do with the way pinning works.
Next, update the package lists with the usual
aptitude update
and make sure both Lenny and Sid lists are downloaded.
Finally, install the WebGUI packages doing
aptitude -t sid install webgui
This will pull webgui and libjs-yui from Sid, but the rest of the packages will be pulled from Lenny. There are newer versions for several Perl modules available in Sid, so you might want to add them to your pinning configuration if you're interested in using them, but YMMV.
Database and Apache setup
Check /usr/share/doc/webgui/README.Debian.gz for instructions on database and Apache setup.
Assisted database creation is a work in progress for the Debian package, so in the mean time you'll have to do it manually. The appropiate commands are spelled out for you in README.Debian.
The Debian package cannot assume WebGUI to be the only Apache application, so it provides a couple of sample config files for you to use, and also a couple of Apache modules need to be enabled. Again, the appropiate commands a configuration suggestions are spelled out for you.
The default configuration will have WebGUI running under http://localhost/webgui. If you want to change the root location or have WebGUI take control of the webserver, you'll need to use the alternate configuration file.
WebGUI and the FHS
Debian's WebGUI package strictly follows the FHS, so instead of a /data with everything inside, things are spread out. This means:
* WebGUI libraries are in /usr/share/webgui
* WebGUI log files are in /var/log/webgui, and get rotated automatically thanks to Debian's logrotate configuration.
* WebGUI configuration is in /etc/webgui.
* WebGUI web content is in /var/lib/webgui
* WebGUI utility scripts are in /usr/bin with a wg- prefix, i.e. wg-upgrade instead of plain upgrade.
* Spectre, being a daemon lives in /usr/sbin, and can be handled using /etc/init.d/webgui or through the usual way.
* Every utility script has a proper man page.
* WebGUI will use TinyMCE's as packaged by Debian and not as provided by WebGUI.
* WebGUI will use YUI as packaged by Debian and not as provided by WebGUI.
It also means you cannot start with a Debian package install and then upgrade to a non-Debian package install (WRE or source) unless you know exactly what you are doing.
Indexing and spelling
The Debian package sample WebGUI configuration already has support for PostScript and PDF indexing, so you need not do anything special. Just upload PostScript and PDF files and WebGUI will be able to index them out of the box.
If you want to enable the spell checker, just install as many aspell dictionaries as you want (aspell-en, aspell-es, aspell-de, etc.) and follow the instructions in /usr/share/doc/webgui/README.Debian.gz to enable them.
Bugs? What bugs?
Debian packaging is not done by Plainblack, so if the Debian package is not working for you, something is missing, or you have suggestions in order to improve the packaging, please file a Bug in the Debian BTS or contact the package maintainer (look at /usr/share/doc/webgui/changelog or for SquOnk on IRC).
Comentarios