Parisian Posted January 25, 2018 Posted January 25, 2018 This will allow easy integration via services like Packagist. aia 1
Aiwa Posted January 25, 2018 Posted January 25, 2018 (edited) 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. Edited January 25, 2018 by Aiwa MADMAN32395 1
Parisian Posted January 26, 2018 Author Posted January 26, 2018 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.
Aiwa Posted January 26, 2018 Posted January 26, 2018 So I understand your argument, piracy will always exist, so let's make it easier for them? Did I interpret that right? Rhett, BomAle and AlexWright 3
Parisian Posted June 18, 2018 Author Posted June 18, 2018 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. PurplePixel and aia 1 1
AncientMariner Posted July 29, 2020 Posted July 29, 2020 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. aia and PurplePixel 2
PurplePixel Posted November 17, 2020 Posted November 17, 2020 (edited) 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. Edited November 17, 2020 by PurplePixel
Recommended Posts