sHagen wrote:Hello,
I deployed imagevue X3 on a
lighttpd webserver with the following rewrite rules:
I have trouble to decode the apache rewrite rules. I think it would be great if we could assemble some sort of documentation about how the rewrite should work. The various admins usually know their server software and then they can implement it without learning the apache ruleset first.
Generally speaking, this is documentation we need to catch up on at some point. I can't give clear answers specifically about lighttpd unfortunately. We are still busy getting out the new website, and 99% of our users are on standard shared Apache servers.
I am curious, is this your own server? And if so, is this also your server for live production websites?
sHagen wrote:The first rewirte rule forwards to the "homepage", which is /wedding/ in my case. I didn't find a setting in Imagevue X3 to do this automatically. I'm sure it's there.
Really not sure what you are trying to do here. Your home page should always be / INDEX (root domain), or the root of the folder where you installed X3. If it's not, then why not just install X3 in a folder called /wedding/ in the first place, if that is your home page? It is not good practice to redirect like this, as it creates unnecessary requests, and provides robots (SEO) inaccurate data. Also, with the X3 ASSETS settings, you could load images from weddings into your actual index home page. What you are requesting, it to not have a home page at all, and instead redirect all requests to the homepage, to your wedding page.
sHagen wrote:On a brand new install, the diagnostics in Imagevue X3 is killing my php-fpm process entirely. I have to first start up without rewirte rules, go to the panel, deactivate diagnostics, activate the rewrite rules and then everything works just fine.
Can't say anything about this unfortunately. If you check app/x3.diagnostics.php, it is a very simple script that checks extensions, and creates a few cache folders if necessary. Not much we can rewrite in this code ... sounds like something server-specific.
sHagen wrote:I'm unsure about....
"^/app/" => "/index.php",
This seems to be used for the email process, which is currently not working in this setup.
I'm also not sure about
/public/* and
/check/* as I have not seen any links using them.
I believe all rules mentioned above can be ignored/removed, as they are part of legacy methods. X3 makes direct requests to files in "public", so no need to include the rule for that ... It's just generally part of the idea that all your public assets should be contained within /public/ and a request to /image/somefile.jpg will check for /public/image/somefile.jpg if rule is enabled. Can't see that there are any rules for /check/ any longer, as this was a folder in a previous version of X3 ...
sHagen wrote:I have trouble to decode the apache rewrite rules. I think it would be great if we could assemble some sort of documentation about how the rewrite should work. The various admins usually know their server software and then they can implement it without learning the apache ruleset first.
Sure. Will get around to it as soon as we find time.
