Spin-native Support for Private Composer Packages #164
luchfirearmland
started this conversation in
Ideas
Replies: 1 comment 1 reply
-
I solve this by running the composer auth config inside the container using spin run. No need to tinker with Dockerfile.php.
This way, no permission issues, no need to persist auth.json, and works fine in both local and CI. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
👉 Describe the problem
Hi! Someone is having a problem with installing a FilamentPHP Plugin that he purchased. I also have the same issue in the future as I will need to install a private package as well.
Discord Chat: https://discord.com/channels/910287105714954251/910299290230997003/1398290085908054139
👥 Problem evidence & reach
According to that chat above, here' the error he got when trying to install that private package.
🥰 Describe the "impact" on users?
This is very important to developers who use private packages to save time with the development. I have also tried making a private package before hosted at GitLab Private Composer packages or something. There are also a lot of private Laravel-related packages out there especially related to FilamentPHP and Statamic, so I'm sure they'll be bummed out if their favorite package cannot be installed.
🏆 How to solve this problem
This might involve tinkering with the
Dockerfile.php
so we can addauth.json
somewhere that the Composer CLI will recognize.💯 How do we validate the problem is solved?
The problem is solved if we can install packages from private Composer repositories.
Beta Was this translation helpful? Give feedback.
All reactions