@maxacarvalho If I was going for an individual site deploy, I'd likely just check in everything but vendor, storage, and .env into git and deploy/composer install the files. However my goal from the beginning when I migrated to OctoberCMS was to build reusable, versioned plugins that I can add to client sites. My clientele are all fairly niche and have a pretty large overlap in functionality. The challenge here is that I'm using private bitbucket packages - which is why I went the satis route. If all of your plugins are open source you could skip that step.
I build my plugins based on common default functionality and use semantic versioning to ensure compatibility requirements. With my setup I'm able to composer require my themes into a fresh octobercms install which will automatically install all of their plugin dependencies. If I deactivate core updates, I can run composer update at will without worrying about pushing any package or plugin beyond its limits.
Similarly selling new non-breaking functionality to a client means updating their site's composer.json with the new plugin version (e.g. v1.5 instead of v1.2), running a composer update, php artisan october:up, and having it auto implement to their server. Enjoy your new widget or import/export!
This might be overly complicated for a one-off site but my motivation was moving a web agency from an outdated, non-modern cms to something that can hopefully make things easier to build and update. If anyone has any questions about my experiences, feel free to ask. I'm still perfecting my process but I'm really pleased with how it is working.
Last updated