I have had an ongoing litany of issues, particularly relating to the deployment of the completed October site. In fact, it has now taken me nearly as long to get a site successfully deployed as it has taken me to learn October, build the layout and implement it in October CMS. When I say "successfully" I should probably point out that I have in no way succeeded.
I should point out that I prefer to use Heroku and similar PaaS solutions. They work for me, as Heroku has no cost for startup apps, by comparison to a $5 a month cost for Digital Ocean, etc. If October is not compatible with Heroku that's one thing, but I'm not sure why that would be the case and the issues that are occurring seem to be failures on October's part, not Heroku's. I should also not that yes I am aware that October is beta software. This post could be considered beta feedback. This is a severe (completely blocking, I may have to abandon October entirely) issue that is occurring with deployed October instances.
Initially I posted to state my issue - the lack of a composer.json in the installer left me with no way to deploy to Heroku. Attempting to just add a composer.json file and update/deploy from that resulted in fatal errors in composer. In the end I was forced to start again, creating a new local development host from the command line. That all worked fine and I continued with successful development until the project was near complete. I then went to deploy my code to a heroku app.
It is at this point the wheels fell off.
The code I used had a plugin - Rainlabs Blog. This caused a number of nasty errors. Most severely:
RainLab\Blog\Models\Category and October\Rain\Database\Traits\Validation define the same property ($rules) in the composition of RainLab\Blog\Models\Category. However, the definition differs and is considered incompatible. Class was composed
This exception was all I could get to show, and I have posted it to the plugin's forum, with no response so far. Indeed, due to what I would have to describe as a namespace clusterfuck I was unable to find the conflicting files for some time, and even then have not been able to actually resolve the issue. I had installed the plugin by adding the plugin to the project. It was at this point that I found that while you can add a plugin to a project, removing a plugin from a project is not possible. This needs to be possible, as any attempt to update October re-added the plugin, causing the update to fail with the above error.
Weirdly, this error occurred only in the online version of the site. My local version runs 5.4, while heroku appears to be running 5.6RC. An odd choice, to be honest. I tried everything I could think of, deleting the files and db tables manually, git deleting them, reinstalling through the interface or by downloading... everything. In the end the only choice I had was.. simply to give up.
I yet again commandline composer installed the repo, copying over the theme with its content and began a whole new heroku app as well. This time I was careful to keep the plugins out of the repo, and installed it in the production backend.
I have not gotten the above error. I went to the site and had a look around and for the most part it made sense. A missing component on the contact page created an error, so I installed that plugin too and fixed that problem. Then I started browsing around, and found... suddenly everything doesn't work.
Class 'Cms53c7fe72c755c_4288314767Class' not found /app/themes/toughguy/layouts/default.htm line 151
I'm not sure what is causing this, but it appears to be a pre compiled class possibly generated by Twig? I have fixed this error in the past by simply opening up the template and making a trivial change and then saving it again. That seems to work in this case, but as soon as I go to any other page it simply gets the same error. I attempted to resolve this by using October's artisan clear cache command. While this claimed to have cleared a bunch of caches it doesn't seem to have resolved any issues.
If anyone has any actually useful suggestions, or some sort of workflow for October deployment that actually works, I'm all ears. After five days of chasing my tail on deploying an otherwise working project, I'm getting pretty desperate.