MODX Installer - to install any version of MODX quickly

Thanks Susan and pathologic,
I called the host and they gave me info on how to add an .ini file to turn the allow_url_fopen on. And then no problem running it on the four sites hosted there. I have a few other problem child sites on other hosts but all in all I AM THRILLED with this. I think it will be great and a very needed script. THANK YOU

Hi Folks!

I used this installer and thought it was kinda' cool until I found that the housekeeping is a bit lacking - too bad too because I have a couple of clients that only have SFTP or SSH access. In any case I found a folder called _build that was left behind and almost all of my clients favicons were overwritten with some icon that's included in the package. Getting some of the icons back was no big deal - others were a PITA.

Could the author clean that up?

Hi Folks!

I used this installer and thought it was kinda' cool until I found that the housekeeping is a bit lacking - too bad too because I have a couple of clients that only have SFTP or SSH access. In any case I found a folder called _build that was left behind and almost all of my clients favicons were overwritten with some icon that's included in the package. Getting some of the icons back was no big deal - others were a PITA.

Could the author clean that up?

Hi Folks!

I used this installer and thought it was kinda' cool until I found that the housekeeping is a bit lacking - too bad too because I have a couple of clients that only have SFTP or SSH access. In any case I found a folder called _build that was left behind and almost all of my clients favicons were overwritten with some icon that's included in the package. Getting some of the icons back was no big deal - others were a PITA.

Could the author clean that up?

Hi Folks!

I used this installer and thought it was kinda' cool until I found that the housekeeping is a bit lacking - too bad too because I have a couple of clients that only have SFTP or SSH access. In any case I found a folder called _build that was left behind and almost all of my clients favicons were overwritten with some icon that's included in the package. Getting some of the icons back was no big deal - others were a PITA.

Could the author clean that up?

Quote from: nitrojane at Mar 13, 2014, 01:07 PM

Hi Folks!

I used this installer and thought it was kinda' cool until I found that the housekeeping is a bit lacking - too bad too because I have a couple of clients that only have SFTP or SSH access. In any case I found a folder called _build that was left behind and almost all of my clients favicons were overwritten with some icon that's included in the package. Getting some of the icons back was no big deal - others were a PITA.

Could the author clean that up?

Nitrojane, the script only downloads and unpacks distros - so _build folder issue is not connected with it (:
The authors are from Evo community, so it would be better to send pull requests about Revo.
By the way, you can find useful these shell scripts created for Revo (and nginx, but there are links for apache2):
https://gist.github.com/bezumkin/2179479
https://gist.github.com/bezumkin/2179440
https://gist.github.com/bezumkin/2179492

At the risk of being argumentative - it does leave that folder and does clobber my favicon if it's on the root of the folder system.
Could be this particular ISP and/or php or other things. PM me for a demonstration.


Quote from: pathologic at Mar 13, 2014, 01:53 PM

Quote from: nitrojane at Mar 13, 2014, 01:07 PM

Hi Folks!

I used this installer and thought it was kinda' cool until I found that the housekeeping is a bit lacking - too bad too because I have a couple of clients that only have SFTP or SSH access. In any case I found a folder called _build that was left behind and almost all of my clients favicons were overwritten with some icon that's included in the package. Getting some of the icons back was no big deal - others were a PITA.

Could the author clean that up?

Nitrojane, the script only downloads and unpacks distros - so _build folder issue is not connected with it (:
The authors are from Evo community, so it would be better to send pull requests about Revo.
By the way, you can find useful these shell scripts created for Revo (and nginx, but there are links for apache2):
https://gist.github.com/bezumkin/2179479
https://gist.github.com/bezumkin/2179440
https://gist.github.com/bezumkin/2179492

And my apologies - thanks for the links and suggestion!

Quote from: nitrojane at Mar 13, 2014, 02:29 PM

At the risk of being argumentative - it does leave that folder and does clobber my favicon if it's on the root of the folder system.
Could be this particular ISP and/or php or other things. PM me for a demonstration.


Quote from: pathologic at Mar 13, 2014, 01:53 PM

Quote from: nitrojane at Mar 13, 2014, 01:07 PM

Hi Folks!

I used this installer and thought it was kinda' cool until I found that the housekeeping is a bit lacking - too bad too because I have a couple of clients that only have SFTP or SSH access. In any case I found a folder called _build that was left behind and almost all of my clients favicons were overwritten with some icon that's included in the package. Getting some of the icons back was no big deal - others were a PITA.

Could the author clean that up?

Nitrojane, the script only downloads and unpacks distros - so _build folder issue is not connected with it (:
The authors are from Evo community, so it would be better to send pull requests about Revo.
By the way, you can find useful these shell scripts created for Revo (and nginx, but there are links for apache2):
https://gist.github.com/bezumkin/2179479
https://gist.github.com/bezumkin/2179440
https://gist.github.com/bezumkin/2179492

Went back to github to see if a newer version of the installer was there - it is - and the new version does not leave the artifacts and the icon is not touched.
Had no idea the script had been updated.

Thanks,

Jane



Quote from: nitrojane at Mar 13, 2014, 02:32 PM

And my apologies - thanks for the links and suggestion!

Quote from: nitrojane at Mar 13, 2014, 02:29 PM

At the risk of being argumentative - it does leave that folder and does clobber my favicon if it's on the root of the folder system.
Could be this particular ISP and/or php or other things. PM me for a demonstration.


Quote from: pathologic at Mar 13, 2014, 01:53 PM

Quote from: nitrojane at Mar 13, 2014, 01:07 PM

Hi Folks!

I used this installer and thought it was kinda' cool until I found that the housekeeping is a bit lacking - too bad too because I have a couple of clients that only have SFTP or SSH access. In any case I found a folder called _build that was left behind and almost all of my clients favicons were overwritten with some icon that's included in the package. Getting some of the icons back was no big deal - others were a PITA.

Could the author clean that up?

Nitrojane, the script only downloads and unpacks distros - so _build folder issue is not connected with it (:
The authors are from Evo community, so it would be better to send pull requests about Revo.
By the way, you can find useful these shell scripts created for Revo (and nginx, but there are links for apache2):
https://gist.github.com/bezumkin/2179479
https://gist.github.com/bezumkin/2179440
https://gist.github.com/bezumkin/2179492

The installer.php script does absolutely nothing more than fetch the indicated MODX zip file, unzip it, and redirect the browser to the MODX setup/install directory. Any leftover _build files or overwritten files are due to the MODX installer/setup, and will do exactly the same thing if you upload and extract the MODX .zip file yourself.

The main flaw with this installer.php script is that it doesn't do anything about a failed download. There is the try/catch in the download function, but nothing is actually done with it.