Skip to content

RFC: Update Dockerfile for --classmap-authoritative #828

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

Closed
wants to merge 1 commit into from

Conversation

94noni
Copy link
Contributor

@94noni 94noni commented Aug 19, 2025

RFC: is this ok and similar ?

leverage --classmap-authoritative with install not via independent dump-autoload

@7-zete-7
Copy link
Contributor

Hi @94noni!

I see two problems:

  • The --classmap-authoritative option will be ignored due to the presence of the --no-autoloader option.
  • Generating an autoloader at the time of executing the composer install … command of this Dockerfile will not dump the correct autoloader because the project files do not exist at this moment.

@94noni
Copy link
Contributor Author

94noni commented Aug 19, 2025

@7-zete-7 hum ok I see very well with explanations thank you
is this also the reason why --no-autoloader is defined ? so the dump autoload do it later ?

@7-zete-7
Copy link
Contributor

@94noni yes, you got that right
IMO this is a clever optimization of the container build

@94noni
Copy link
Contributor Author

94noni commented Aug 19, 2025

fair thx for answering !
lets close then :)

@94noni 94noni closed this Aug 19, 2025
@94noni 94noni deleted the patch-1 branch August 19, 2025 13:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants