Closed scith closed 9 years ago
Even without the trailing slash it seems that the install script cannot be ran. I don't know why, if I put the install.php file back in the folder after the app was installed, I can run the functions in the script and it works.
In the app install log, the "token" is empty however.
Let me take a look at it, I'll come back to you if I find something concrete.
Le 20/08/2015 17:39, Jeff a écrit :
Even without the trailing slash it seems that the install script cannot be ran. I don't know why, if I put the install.php file back in the folder after the app was installed, I can run the functions in the script and it works.
In the app install log, the "token" is empty however.
— Reply to this email directly or view it on GitHub https://github.com/matlink/pluxml_ynh/issues/12#issuecomment-133054981.
Check the last commit (https://github.com/matlink/pluxml_ynh/commit/6dd6e0396b357f29c1e8e93fe39ac757633242e2), it should do the trick.
It works great thanks :) Now I can install several PluXml on various subdomains!
.htaccess is obsolete with nginx, since it does not use this kind of file to manage writes. Finally I'm removing it cause this is sensless.
Hello, I have a bug when trying to install PluXml on the path "/" (root of a domain). I think it breaks the install script and the nginx file. In the Nginx file I have things like "//data" (one extra trailing slash.
I look at the install script and I think the same problem occurs: curl -kL -o install_page.html https://DOMAIN//install.php
I think at some point you need to add: "path=${path%/}" to remove the trailing slash.
Thanks