Hello Gabriele,
On 2012-12-17 11:29, Gabriele wrote:
So give me a very good reason to rewrite all of them and introduce a
new 'sitedir' variable.
Maybe where someone does not have control over the DNS server.
There are cases where piler runs on a machine that is not dedicated,
for
example in soho situations, where there are no high loads but email
archiving is important ...
come on, is it really difficult for a soho in 2012 to get a DNS record
done?
Anyway I made a test installation and managed to put everything under
/kkk/ directory.
However there are some pitfalls:
- you can't just remove the starting '/' from the images in mini.css
and style-default.css
since they have to be referenced by absolute URIs.
- the .htaccess file also must be fixed manually
The only solution that makes sense to me can be if I set a fixed
pathname, eg. http://your.fqdn.com/mailpiler/, so everybody has to use
this URL to access the web ui. (But this would break those installations
where piler is installed to the documentroot). Otherwise you have to
adjust it for yourself.
So my offer is that I can make most of the webui files support the
subdirectory thing, if this is really a show stopper, but still the
tradeoff is that you have to fix the .htaccess file, and the css files
on your own at each upgrade.
So I still believe that installing piler right into the documentroot is
the preferred way.
Frankly it's *much* easier to me to provide you a domainname pointing
to an IP-address of your choice in a subdomain under mailpiler.com thus
enabling some difficult customers to get it right.
Janos
