Document local migrations, mention --wait for cf migrations

This commit is contained in:
rachidatecs 2023-05-17 18:41:52 -04:00
parent a3606d6497
commit f60f2bff05
No known key found for this signature in database
GPG key ID: 3CEBBFA7325E5525

View file

@ -12,19 +12,32 @@ to get a `psql` shell on the sandbox environment's database.
## Running Migrations ## Running Migrations
### On Local
```shell
docker-compose exec app bash
./manage.py makemigrations
```
The docker compose down then up to run the new migrations.
### On Cloud.gov
When new code changes the database schema, we need to apply Django's migrations. When new code changes the database schema, we need to apply Django's migrations.
We can run these using CloudFoundry's tasks to run the `manage.py migrate` We can run these using CloudFoundry's tasks to run the `manage.py migrate`
command in the correct environment. For any developer environment, developers command in the correct environment. For any developer environment, developers
can manually run the task with can manually run the task with
```shell ```shell
cf run-task getgov-ENVIRONMENT --command 'python manage.py migrate' --name migrate cf run-task getgov-ENVIRONMENT --wait --command 'python manage.py migrate' --name migrate
``` ```
(The optional 'wait' argument will wait until the environment is stable)
Optionally, load data from fixtures as well Optionally, load data from fixtures as well
```shell ```shell
cf run-task getgov-ENVIRONMENT --command 'python manage.py load' --name loaddata cf run-task getgov-ENVIRONMENT --wait --command 'python manage.py load' --name loaddata
``` ```
For the `stable` environment, developers don't have credentials so we need to For the `stable` environment, developers don't have credentials so we need to