Hello,

I setup an OctoberCMS installation recently for a client of mine on Heroku. The problem is that due to Heroku's ephemeral file system, any plugins that my client installs themself is removed upon a redeployment to Heroku.

Are there any suggestions for getting around this? Uploading the plugin files to Github and deploying that way isn't a great solution for my client.

Thank you!

@ryan.simon62317 I've been investigating using Heroku with October CMS recently, and unfortunately I don't believe it's easily done. October CMS, with its flat-file structure for themes and plugins, simply isn't compatible with Heroku's ephemeral storage.

From what I can tell, most external storage with Heroku involve using AWS S3 for storage, which is supported in October CMS only for media and uploaded files, but not for plugins and themes. If the client were willing to keep plugins and themes in the repo, it's theoretically possible to use that to deploy and keep active the themes and plugins, but they wouldn't be able to use the CMS features in the backend, nor run plugin updates and the like.

Note that if they have a database setup they could use the databaseTemplates feature to persist theme / static content changes even across deployments although you'll still have issues with any added plugins / themes by the client through the CMS.

Thanks guys, I appreciate the quick feedback on that. I decided to move the project to CloudWays instead as it seems that will be a better fit for this particular install.

@ryan.simon62317

Nice one! Best of luck :)