I am using Envoyer.io to manage my October site and each time you push a new commit to the server, it creates a brand new folder of the site and redeploys it. This means that no "existing" plugins will ever be on the new update of the site because the previous plugins are in a totally separate folder. So unless you have all the plugins actually inside of the git repo, each new commit will never actually have any plugins installed. Now this would easily be fixed if there was a way to run essentially an "install plugins" artisan command like the backend allows you to do via "Force update".

With Envoyer, you just set up deployment hooks so after "install composer dependencies" I would just throw in the artisan command to install plugins and then it would activate the new release. Well I tried throwing php artisan october:update in there and it works as expected, except for the fact that it doesn't update any plugins because there aren't "technically" any installed.

I can't seem to find an artisan command that just installs the plugins, from the documentation it appears that you need to run php artisan plugin:install AuthorName.PluginName for each plugin to accomplish this. There doesn't appear to be any mass "install all plugins tied to this site" (my project is attached to my octobercms.com account so it should know what plugins need to be installed).

Again, however "force updates" does it on the back-end, is there any way to essentially run a "force updates" from the command line? or at the very least, somehow "install all plugins" tied to the site?

Without this option, this requires you to essentially HAVE to version control all of your plugins in the repo, otherwise they won't be pulled to the new site update. Or you have to do a an awkward fix which consists of creating a symlink folder that directs the plugins folder to storage/plugins because the storage folder is stored outside of the site folder. But having all the plugins sitting in storage/plugins feels a bit "wrong" to me, but maybe it isn't?

Last updated 8 years ago

Hi, how did you end up solving this problem?

You should set your project ID first. This is how my deploy script looks like:

composer install --no-interaction
php artisan october:up
php artisan october:util set project --projectId=your_project_id
php artisan october:update
php artisan october:up
php artisan theme:use your_theme

Last updated 4 years ago