Managing plugin in main project composer.json when under Development.

[jeremyzahner]

For a project i use herbert with i am having the following situation:

• Project is "live" on a staging server, including the plugin.
• Plugin is still under development but locally linked as a symlink
• Deployment happens via Capistrano

My Problem: I need to add the plugin and its repo in the main projects composer.json so it gets deployed right onto the staging server. On the other hand i dont want composer to overwrite my local symlink every time i run composer update.

Is there a easy way for this? I assume that im not the first person having this issue. Im also aware that this is not necessarily a Herbert Issue.

Thanks for you best practices!

[JacobDorman]

Haven't been able to find an acceptable 'best-practice' solution to this problem with composer, but for a single plugin i'm using the following workaround:

• no symlink, plugin repo in actual plugin directory. Live development, without push and composer update
• dev-master in main composer.json (switch to tagged release once released)
• mv web/app/plugins/myplugin myplugin before local composer update (otherwise composer complains of no composer remote)
• rm -rf web/app/plugins/myplugin && mv myplugin web/app/plugins/ after.

It's not pretty, but it works for now.

[jeremyzahner]

@jasonagnew @onnimonni We should find a valuable best practice for this issue.