ParisianJanuary 25, 2018 in Feedback
This will allow easy integration via services like Packagist.
Why? IPS software isn't publicly available unless you've purchased a license. The source code would still have to be behind a client login.
It makes integration easier and people will always be able to obtain the source code illegally. It just makes development and upgrades easier for those of us who pay for the software.
So I understand your argument, piracy will always exist, so let's make it easier for them? Did I interpret that right?
I don't think you understand how composer works, we will add a custom URL with our authorisation tokens for our projects which will fetch directly from Invision's servers directly. It's no less secure than how the current update system is implemented already, just provides another method of integration.
I'd just like to raise this thread from the dead and add a +1. Modern PHP apps use Composer. We extend IPB a bunch and it's hacky atm. Having IPB be accessible via composer would make updating IPB much easier too. It's totally fine if the packages were behind a client login, very used to this on other projects.
I'm definitely supporting this - standardising IPB would make development and even contribution much simpler. I understand there are many challenges to make this possible but it would have compounding benefits in the future.
Started April 7, 2019
Started May 14, 2018
Started January 11, 2020