https://wiki.alessandro.delgallo.net//index.php?action=history&feed=atom&title=Webapp-config 2026-09-15T07:01:08Z Revision history for this page on the wiki MediaWiki 1.37.1 https://wiki.alessandro.delgallo.net//index.php?title=Webapp-config&diff=3751&oldid=prev 2010-11-09T13:13:56Z

<p>Created page with &#039;Actually this page was entirely copied from: http://www.elvanor.net/wiki/Webapp-config ( A guy like me I suppose) = General = * webapp-config is a Gentoo only tool to allow a ...&#039;</p> <p><b>New page</b></p><div>Actually this page was entirely copied from: http://www.elvanor.net/wiki/Webapp-config ( A guy like me I suppose)<br /> <br /> = General =<br /> <br /> * webapp-config is a Gentoo only tool to allow a single web applications to be correctly installed into multiple virtual hosts. This is nice as it allows the code to remain on a standard, Portage managed place while you can easily deploy your web applications into production.<br /> <br /> * Currently the way it works is by creating a directory corresponding to the application inside the specified virtual host. By default it will be installed in /var/www/&lt;virtual_host_name&gt;/htdocs; you can configure that by editing /etc/vhosts/webapp-config. I use the following convention:<br /> <br /> vhost_root=&quot;/srv/${vhost_subdomain_2}.${vhost_subdomain_1}/&quot;<br /> vhost_htdocs_insecure=&quot;./&quot;<br /> <br /> * In /etc/vhosts/webapp-config, you need to have a vhost_hostname variable that can conform to a fully qualified domain, eg localhost won't work. Put something like &quot;elvanor.net&quot; there.<br /> <br /> * The only problem is that webapp-config always creates icons, error, and cgi-bin directories in the virtual host directory if they are not there. I would prefer that not to happen.<br /> <br /> = Installing, checking =<br /> <br /> * Typical installation:<br /> <br /> webapp-config -I -h shoopz.com -d wordpress wordpress 2.7.1<br /> <br /> * To check what are the current installations of a given application (you can optionally specify a version):<br /> <br /> webapp-config --li wordpress 2.8<br /> <br /> * To check unused installs (very useful):<br /> <br /> webapp-config --lui wordpress<br /> <br /> = Updating =<br /> <br /> * When you need to update a web application, use the -U switch, eg:<br /> <br /> webapp-config -U -h elvanor.net -d phpmyadmin phpmyadmin 2.11.5<br /> <br /> * If you use a directory different that the application name, don't forget to change that. However note that by convention that should not happen.<br /> <br /> webapp-config -U -h www.elvanor.net -d www/mediawiki mediawiki 1.13.3<br /> <br /> == Important warnings ==<br /> <br /> * Updating a web-application can sometimes remove the configuration files! Be sure to systematically check (this is the case with Wordpress, although it seems to be a bug). Also, any changes to the DB must usually be done manually.<br /> * '''emerge --depclean''' will remove *installed* versions of a webapp package if a newer one has been already merged! Thus update all your web-applications before running emerge --depclean.<br /> * Running webapp-cleaner should also be done before emerge --depclean.<br /> <br /> = Cleaning =<br /> <br /> * The application webapp-cleaner can be used to remove old versions of an webapp package.<br /> * Manual removal of a web-app (there may be some leftover files):<br /> <br /> webapp-config -C -h shoopz.net -d bugzilla bugzilla 3.0.5</div>

Porcelinux