This problem is kind of a theme with any of the PHP based applications. These days, almost anyone running a server on the internet is going to be running LAMP stack applications in a virtual hosting configuration where they have more than one instance of Wordpress, Drupal, Mediawiki, etc. etc. on a single server. The Debian packages are generally not well suited to this use case. The solution isn't particularly clear because many of these systems want to modify their own files to store configuration, which is a violation of policy.
It would be nice to re-architect the way these LAMP apps work so that they are a "template" and you can install instances of them that would appear in sites-enabled. Unfortunately, that is starting to stray deep into configuration management territory. ----- "Raphael Hertzog" <hert...@debian.org> wrote: > The package is relatively up-to-date in testing/unstable. Obviously > stable is another story. > > That said I have no experience with updates through the dashboard and > it's not something that is likely to be supported by Debian. We much > prefer > updates through packages. > > But having working themes and plugins available through symlinks > in /var/lib/wordpress is something that I'd like to get working. > > That said for non-packaged plugins/themes, you should have the real > files in /var/lib/wordpress/ and not symlinks... so I'm not sure what > you are having trouble with. Is it only the dashboard-based update > that is > not working well for you? -- Ean Schuessler, CTO e...@brainfood.com 214-720-0700 x 315 Brainfood, Inc. http://www.brainfood.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
