Log message #4049704

# At Username Text
# Jul 10th 2017, 09:42 birdy247 If I remove this from my bootstrap.php a few plugins dont work
# Jul 10th 2017, 09:41 birdy247 The ControllerFactory
# Jul 10th 2017, 09:40 birdy247 Ah, fixed it :slightly_smiling_face:
# Jul 10th 2017, 09:33 birdy247 I just get a 500
# Jul 10th 2017, 09:30 birdy247 but my app isnt loading
# Jul 10th 2017, 09:30 birdy247 I just turne on middleware
# Jul 10th 2017, 09:18 cleptric Aynone using graylog with an cake app?
# Jul 10th 2017, 09:06 kareylo Hello
# Jul 10th 2017, 08:44 maymeow @neon1024 @admad ty
# Jul 10th 2017, 08:44 admad gtg
# Jul 10th 2017, 08:43 admad *avoiding
# Jul 10th 2017, 08:43 admad @maymeow avoid git submodules and using packagist for private packages is good. Just don't develop the plugins under app's vendor
# Jul 10th 2017, 08:37 maymeow @admad @neon1024 's looks like good idea but when you told composer can delete or make changes in local folder i think i go back to my old way :slightly_smiling_face:
# Jul 10th 2017, 08:35 admad @maymeow that's fine, just don't use composer's "vendor" folder for plugin development
# Jul 10th 2017, 08:34 admad one day i might have the change to told you "i told you so"
# Jul 10th 2017, 08:34 maymeow @admad before i had plugin folder ignored, and all plugins had their own git repo
# Jul 10th 2017, 08:33 admad sure keep doing what you like. But i would advise @maymeow to follow the safer option
# Jul 10th 2017, 08:33 neon1024 I guess it’s whichever workflow you like best :slightly_smiling_face:
# Jul 10th 2017, 08:33 admad using the "vcs" option
# Jul 10th 2017, 08:32 admad you can always tell composer to use the separate folder as source
# Jul 10th 2017, 08:32 neon1024 As unit testing a plugin inside an application can be problematic :slightly_smiling_face:
# Jul 10th 2017, 08:32 neon1024 The better reason is for testing
# Jul 10th 2017, 08:31 neon1024 It will even prompt you if the folder has changes
# Jul 10th 2017, 08:31 neon1024 I’ve not seen composer wipe out a folder before
# Jul 10th 2017, 08:30 admad everything under "vendor" should be disposable
# Jul 10th 2017, 08:29 admad if composer decides to wipe out the folder during update/install and you have local changes to plugin not pushed to server they would be lost
# Jul 10th 2017, 08:29 neon1024 Can you give some examples why? It’s worked well for us for a long while
# Jul 10th 2017, 08:28 admad doing plugin development inside /vendor is a bad idea.
# Jul 10th 2017, 08:28 admad plugin
# Jul 10th 2017, 08:28 neon1024 Which repo though @admad the project repo, or the plugin repo?
# Jul 10th 2017, 08:26 admad @maymeow use separate copy of repo for plugin development
# Jul 10th 2017, 08:04 cjquinn I feel like all the gotchas are covered here - https://book.cakephp.org/3.0/en/controllers/middleware.html#adding-the-new-http-stack-to-an-existing-application
# Jul 10th 2017, 07:56 birdy247 Are there any gotchas I need to look out for
# Jul 10th 2017, 07:56 birdy247 I was going to turn on middle ware
# Jul 10th 2017, 07:56 birdy247 I have just upgraded from 3.3 to 3.4.x
# Jul 10th 2017, 07:54 maymeow I have installed git server + CI + Packagist for private repos. After commit to server CI commit changes to Github for public repos.
# Jul 10th 2017, 07:52 neon1024 We use a private internal Packagist server for our private packages
# Jul 10th 2017, 07:52 neon1024 If you are developing plugins which are not using Composer, they should be in `/plugins`
# Jul 10th 2017, 07:51 neon1024 https://getcomposer.org/doc/03-cli.md#update
# Jul 10th 2017, 07:51 neon1024 Then when you’re done, just update the `composer.json` to the tag you need and update
# Jul 10th 2017, 07:51 neon1024 Then we can work in the plugin inside `/vendor` and push changes and tags back up directly from the vendor folder