Closed lloricode closed 5 years ago
after.sh
on homestead
#!/bin/sh
# If you would like to do some extra provisioning you may
# add any commands you wish to this file and they will
# be run after the Homestead machine is provisioned.
#
# If you have user-specific configurations you would like
# to apply, you may also create user-customizations.sh,
# which will be run after this script.
sudo apt-get install jpegoptim
sudo apt-get install optipng
sudo apt-get install pngquant
sudo npm install -g svgo
sudo apt-get install gifsicle
The problem is here: https://gist.github.com/lloricode/df3ebd9d3a7e175303609455a9b39b4c#file-vagrant-up-7-11-2019-L27-L32
The keys you're mapping to vagrant via Homestead.yaml
Aren't getting inserted properly so therefore the SSH keys the vagrant
user has access to don't have access to your private packagist.
This can be a pretty difficult thing to debug, but it's nothing Homestead can do for you. My advice would be to not run composer operations in the vm, and instead rum them from your localhost.
Versions
Host operating system
Release Linux Mint 19.1 Tessa 64-bit Kernel Linux 4.15.0-54-generic x86_64 MATE 1.20.1
Homestead.yaml
Vagrant destroy & up output
https://gist.github.com/lloricode/df3ebd9d3a7e175303609455a9b39b4c
Expected behavior
It should clone a private package
Actual behavior
Can not clone private package return from
composer install
with php7.2 https://gist.github.com/lloricode/d101968943e47a68d2f88639d450ea48this is
composer.json
:note:
halcyon-laravel/helpers
is dependency fromhalcyon-laravel/base
andhalcyon-laravel/audit-history
Steps to reproduce
vagrant destroy --force
git checkout v9.0.3
while having latest Settlerv8.0.0
vagrant up
vagrant ssh
cd code/homestead72
composer install