Currently, I have two scheduled machines:
fly m run -r “fra” --env “APP_ENV=production” --env “LOG_CHANNEL=stderr”
–env “LOG_LEVEL=info” --schedule hourly . “php artisan queue:work --stop-when-empty”
fly m run -r “fra” --env “APP_ENV=production” --env “LOG_CHANNEL=stderr”
–env “LOG_LEVEL=info” --schedule hourly . “php” “artisan” “schedule:run”
And some CI/CD from GitHub:
name: Fly Deploy
on:
push:
branches:
- production
jobs:
deploy:
name: Deploy app
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
with:
submodules: recursive
- uses: superfly/flyctl-actions/setup-flyctl@master
- run: flyctl deploy --remote-only
env:
FLY_API_TOKEN: ${{ secrets.FLY_API_TOKEN }}
Can I update the scheduled background workers with the CI/CD?