-
-
Notifications
You must be signed in to change notification settings - Fork 194
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Composer install (PARTIAL) #2353
Conversation
This is the start of moving dependency modules over to composer.
Removing manual load of php-ogp, leaving this for PSR-4 autoloader
Adding PSR Logging library
Adding ToroPHP
Removing PSR logging
Adding MF2 parser, via composer
Adding Swiftmailer 5.2.1
Addung Webignition requirements
Adding font-awesome
Ensuring travis installs dependencies.
Rolling Webignition back to 2.0, since 3.0 is "in no way backwards compatible", and needs PHP 7.2
Looks like we need 1.x
Requiring Bootstrap 3
Using JQuery 3.2.1 from Components repository
Second thoughts, lets require specific versions so that upgrades can be managed
Adding HTMLPurifier library
Installing h5f via composer (from git) This might be a deletion candidate, see idno#2354
Adding JQuery-timeago.js via composer
Adding TinyMCE, pegged to specific version.
Loading symfony class loader from composer
Loading symfony event dispatcher from composer
Loading symfony console from composer
Loading symfony components from composer
Loading SimplePie via composer
Replacing customised AutoP with adopted one.
Mentioning composer when installing directly off of github
Installing version 1.6.0 of underscore.js from github repository
Installing version 1.0.3 of Paypal's accessibility plugin.
Removing IE HTML shiv, since it hasn't been present for a long time.
Installing specific bootstrap toggle version from github
Installing exif-js from GitHub, rolling up to v2.3.0
Installing mediaelement 4.2.6 from github
All changes that are easy to do have been done - other projects don't have clear versions to use. |
Adding support for bower / npm packages, installed via composer.
Tidying up the composer repo by removing the custom repository
Tidying up the composer repo by removing the custom repository
Tidying up the composer repo by removing the custom repository
Tidying up the composer repo by removing the custom repository
Tidying up the composer repo by removing the custom repository
Tidying up the composer repo by removing the custom repository
Tidying up the composer repo by removing the custom repository
Tidying up the composer repo by removing the custom repository
Tidying up the composer repo by removing the custom repository
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we need to have a revamped README / installation documentation to go along with this?
Hmm... I updated the installation docs. Most people seem to install from packages, and for tech users I've got a fatal error that prompts for composer install. Probably good to have in the readme as well... |
Updated |
I think we’ll need to say more - this is literally the bare minimum we could say - but this will work for now. |
Weirdly git seems to have screwed up, and I made the changes but cant push them. |
Come back to the docs - though non-tech users are going to use premade packages |
Here's what I fixed or added:
Moving what I can from /external over to composer
Here's why I did it:
Because it's $CurrentYear, and there are advantages.
This is a PARTIAL conversion, converting most stuff to composer. Remaining stuff is either customised by us, has no clear version to migrate to, or (like mongo) needs some shims on our side to work correctly. So, a migration plan needs to be worked out for these.
Refs #1064
Checklist: