Coming to October from Vanilla Laravel and for some reason deployment has just been a nightmare.

I gather there are some dynamically generated classes that need to stay out of my git repo, but is there any reason why relevant .gitignore's aren't included out of the box? Is there some guide somewhere I'm missing or do I really have to do this piecemeal for every plugin I've developed + the theme? Seems hugely inefficient.

Last updated 8 years ago

What dynamically generated classes are you refering to?

If you want a fully automated deployment and updating process, the first thing you should consider is using the Composer installation method. That provides a solid console interface for further updates and you do not have to rely on the users to manually (or accidently) trigger updates. Dont forget to enable disableCoreUpdates!

The next thing you might want to check out is the Webhooks plugin. Its a pretty simply but cool one. You can set up simple webhooks (fired by your git host probably), that automatically pull in new updates and run the required console commands. You can even create more complex scripts using this plugin.

The same works for themes I guess, however I have never actually tried that.

PS: The only thing that is really required in your .gitignore file (for plugins) is the /vendor folder, as you really dont want to commit that.

Last updated 8 years ago

It just seems backwards that pulling from a repo to deploy from dev>staging>live requires third party plugins and custom code per install. There's no simpler way of doing this?

edit: there's absolutely no way of just pulling down a full install and running a script that will prep it for it's new home? Everything I've read on the forums points to deployment being difficult and my experience so far is bearing that out; an unexpected wart on what otherwise seemed a great framework for deadline driven work.

Last updated 8 years ago

Well, there is one thing that is in the pipe for quite some time now. It is called Private Plugins and enables you to use the Project system introduced by October for custom/private plugins. Im unsure if this is something that will be coupled with so-called 'Pond'. This is a quite easy system, where you attach as many plugins as you want to a project and couple (bind) that to a specifc website. October will then automatically pull these plugins in and updates can be managed through the backend as well.

However, there is no timeframe yet when Pond comes to live and what its specific features will be.

Last updated 8 years ago

jason19962 said: there's absolutely no way of just pulling down a full install and running a script that will prep it for it's new home? Everything I've read on the forums points to deployment being difficult and my experience so far is bearing that out; an unexpected wart on what otherwise seemed a great framework for deadline driven work.

I don't see an issue why you cant write that kind of script. Any installation step or conficuration task can be performed from the command line as well. It'sjust a matter of putting it all together. There will be a paid and hosted solution (which I mentionned in the last post) that probably does all that for you (similar to forge/envoyer), but in the meantime, it should really be no problem that write something that fits your needs ;-)

It's what I ultimately ended up doing. Thanks for the help; so many deadlines >.<.

Although I do think ultimately October needs a more streamlined deployment experience. Still enjoying October more than vanilla Laravel :)