On Mon, 3 Jun 2019 12:13:03 +0200 Alexandre Rossi <alexandre.ro...@gmail.com> wrote: > > I've tried to install adminer using the Debian package. > > I have found the following limitations that seem at least partially related > to this bug report. > > 1) Mandatory adminer/ directory > > I have not found any way to make adminer work without a /adminer/ directory. > > This makes it a bit complicated to to deploy in a custom path or without > exposing the whole /usr/share/adminer even if other files are not required. > > As I understand it, this is what is described in this bug report: the problem > is the hardcoded paths in CSS/js resources.
It looks like Adminer is actually supposed to be compiled from the files included in this package—I was able to get it working using the instructions provided here for Ubuntu 18.04: https://stackoverflow.com/questions/52480057/install-adminer-on-ubuntu-18-04-bionic These instructions don't solve the problem of exposing all the other files over HTTP, however, so after compiling I moved the resulting file to a new subdirectory "/usr/share/adminer/web” and aliased that in Apache rather than the parent directory—once it’s been compiled, it doesn’t look like the paths to CSS and JS files have to be maintained, so this appears to work fine. > 2) No config file support > > I have found no ovious way of configuring adminer using the files from the > Debian package (e.g. enabling a plugin). I think that this issue will go away once you’re using a compiled version rather than the sources, and you’ll be able to use the instructions at adminer.org to customize the configuration. I’ve only just started working with this, so I’m not sure that what I’ve described here is the right way to get everything working, but so far it appears to be the right track. Since there’s no phpMyAdmin package for Debian 10, I suspect that the Adminer package might suddenly start to get a lot more popular. Cheers, Noah
