Skip to content

Commit 2315961

Browse files
committed
Don't run migrations in GH action for Postgres DB
1 parent bf35ac0 commit 2315961

1 file changed

Lines changed: 13 additions & 10 deletions

File tree

.github/workflows/fly-deploy.yml

Lines changed: 13 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -16,13 +16,16 @@ jobs:
1616
- run: flyctl deploy --remote-only
1717
env:
1818
FLY_API_TOKEN: ${{ secrets.FLY_API_TOKEN }}
19-
migrate:
20-
name: Run migrations
21-
runs-on: ubuntu-latest
22-
needs: deploy
23-
steps:
24-
- uses: actions/checkout@v4
25-
- uses: superfly/flyctl-actions/setup-flyctl@master
26-
- run: flyctl ssh console -C 'python manage.py migrate'
27-
env:
28-
FLY_API_TOKEN: ${{ secrets.FLY_API_TOKEN }}
19+
# migrate:
20+
# name: Run migrations if using storage volume
21+
# runs-on: ubuntu-latest
22+
# needs: deploy
23+
# steps:
24+
# - uses: actions/checkout@v4
25+
# - uses: superfly/flyctl-actions/setup-flyctl@master
26+
# - run: |
27+
# # if /data is present, then it is implied that we are using a storage volume, and we should run migrations
28+
# flyctl ssh console -C 'python manage.py migrate'
29+
# shell: bash
30+
# env:
31+
# FLY_API_TOKEN: ${{ secrets.FLY_API_TOKEN }}

0 commit comments

Comments
 (0)