Closed itsmenewbie03 closed 5 months ago
For composer install it's unrecommended to do inside/by package because in case of laravel-updater need also update well be a problem, i recommend running composer install
after php artisan updater:update
For question tow:
In general, i will add it
For composer install it's unrecommended to do inside/by package because in case of laravel-updater need also update well be a problem, i recommend running
composer install
afterphp artisan updater:update
so this means that running composer install
inside
'after_update_pipelines' => [
// you can add your own pipelines here
],
is a bad idea?
yes, it's bad idea you can use this in github action for update automaticity by release
name: deploy to server by ssh
concurrency:
group: production
cancel-in-progress: true
on:
release:
types: [released]
# on: [push]
jobs:
deployment:
runs-on: ubuntu-latest
environment: production
steps:
- name: executing remote ssh commands using password
uses: appleboy/ssh-action@v1.0.3
env:
COMPOSER_ALLOW_SUPERUSER: 1
with:
host: ${{ secrets.REMOTE_HOST }}
username: ${{ secrets.REMOTE_USER }}
password: ${{ secrets.REMOTE_PASSWORD }}
port: ${{ secrets.REMOTE_PORT }}
script: |
cd ${{ secrets.REMOTE_TARGET }}
php artisan updater:update
export COMPOSER_ALLOW_SUPERUSER=1; composer install
as you see i run composer install
after update.
Description
I have the following questions:
composer install
for cases the latest release requires a new package?