[QUESTION]: how to do composer install and a roll back feature? about laravel-updater

[salahhusa9]

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

[salahhusa9]

For question tow:

• roll back: (not supported now) this will be probably a problem if you run migration or seeding, its depend on use case
• update to specific version not latest: (not supported now) this good idea

In general, i will add it

[itsmenewbie03]

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

so this means that running composer install inside

    'after_update_pipelines' => [
        // you can add your own pipelines here
    ],

is a bad idea?

[salahhusa9]

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/[email protected]
        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.