> This is extremely clever. One of the reasons WordPress took off was the easy, non-technical install process.
Ironically Wordpress is a pain in the ass to deploy on "non persistent/deploy with git" PAAS.And uploading plugins directly through the admin is a no go in these cases.
Worpdress wouldnt deploy directly with that one click install,given the fact the configuration is hardwritten on the disk.It would need some refactoring.
You'd need at least to enter some env variables to make things work,and the app would need to detect the db state and run migrations,if not properly initalized,when using a RDBMS(since again,sqlite is out of question on Heroku).
All the same that Wordpress could easily adopt using environmental variables for configuration values to achieve this and simply use a heroku-ified version of config.php. I've used this approach for scaling wordpress sites and its never failed me.
Ironically Wordpress is a pain in the ass to deploy on "non persistent/deploy with git" PAAS.And uploading plugins directly through the admin is a no go in these cases.
Worpdress wouldnt deploy directly with that one click install,given the fact the configuration is hardwritten on the disk.It would need some refactoring.
You'd need at least to enter some env variables to make things work,and the app would need to detect the db state and run migrations,if not properly initalized,when using a RDBMS(since again,sqlite is out of question on Heroku).