-
Notifications
You must be signed in to change notification settings - Fork 6
fix(docker): install the composer dependencies of cloned shipped apps #1064
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
Open
luflow
wants to merge
2
commits into
nextcloud-libraries:main
Choose a base branch
from
luflow:fix/1059/composer-install-for-shipped-apps
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Why not simply:
IF
composer.jsonexistsTHEN
composer install --no-dev?
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.
That was my first attempt, but it breaks on the two different layouts these apps use.
viewerandtexthave a second composer project incomposer/composer.jsonwith"vendor-dir": ".", socomposer/is their vendor dir and it's committed (composer/composer/autoload_real.phpis right there in the repo). Their rootcomposer.jsonis just dev tooling:viewerhas an emptyrequire,textonly requiresphp.notificationsis the newer layout. Rootcomposer.jsonis the runtime project, the vendor dir is the defaultvendorand git ignored, andcomposer/autoload.phpis a hand written shim that requires it.So "root
composer.jsonexists, run install" would install the dev tooling project forviewerandtext, while their actual runtime autoloader incomposer/is already fine. Nothing gets fixed, it just costs time.The bigger problem is the combination with the
rm -rf composerfallback. If that pointless install fails for any reason, we'd delete a committed, working vendor dir and break an app that was healthy. Running the autoloader only touches apps that would really make the server fatal, and it costs twodocker execround trips per cloned app.Happy to go your way if you still prefer it. I'd just keep the fallback behind the autoloader check so a working
composer/can never get removed.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.
Why? I checked both cases and they do not have runtime dependencies.
So yes would waste time but a small amount only because with
--no-devnothing is installed.Why would that be needed? I never had problem cloning any shipped app inside a Nextcloud checkout.
git clone+composer i --no-devalways works for all shipped apps I tried to clone (including text, notifications, activity, viewer, files_downloadlimit etc).Which apps checks in
vendor? This sound not really a good thing to do 👀