Maybe I’m misunderstanding the intended implementation of Cockpit, but I will provide some background first.
I tend to develop web applications in MVC frameworks such as Laravel, Symfony, etc. Often these are basic e-commerce or brochure sites, and for any CMS functionality I build a custom CMS in the admin area.
This works fine up until a point, where the client needs more advanced CMS functionality, in which case it becomes tedious to build more and more bespoke CMS modules.
So then you have the choice of using a CMS-first framework, such as OctoberCMS, Craft or even WordPress. However these are not ideal as you have to build your application around the CMS, instead of the other way round. That’s where the idea of Cockpit appealed to me.
However I’m a bit confused as to how it should be implemented in an MVC framework. Almost all frameworks use Composer to install dependencies, and Cockpit doesn’t seem to come as a Composer dependency - or at least not that I know of.
So the ideal scenario would be for Cockpit to be installed via Composer in to the application vendor folder, and the database / media to exist in the application’s structure itself. This way Cockpit can be safely and easily updated whenever a new release is out and does not need to exist in Git.
Or is this not how Cockpit is meant to be used? Can somebody shed some light on this please?