zydronium/manage.get.gov
1
0
Fork 0
mirror of https://github.com/cisagov/manage.get.gov.git synced 2025-07-20 17:56:11 +02:00
Code Issues Projects Releases Packages Wiki Activity

Updated command instructions in migration doc

Browse source
This commit is contained in:
CocoByte 2023-11-06 14:56:36 -06:00
parent 386300fcaa
commit 350af91ff6
No known key found for this signature in database
GPG key ID: BBFAA2526384C97F
1 changed files with 5 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

10
docs/operations/data_migration.md
View file

@ -216,7 +216,7 @@ This will allow Docker to mount the files to a container (under `/app`) for our
Run the following command, making sure the file paths point to the right location. This will parse the three given files and load the information into the TransitionDomain table. Run the following command, making sure the file paths point to the right location. This will parse the three given files and load the information into the TransitionDomain table.
(NOTE: If working in cloud.gov, change "/app/tmp" to point to the `migrationdata/` directory and remove "./manage.py" from the command) (NOTE: If working in cloud.gov, change "/app/tmp" to point to the `migrationdata/` directory and and remove "docker compose run -T app" from the command)
```shell ```shell
docker compose run -T app ./manage.py load_transition_domain /app/tmp/escrow_domain_contacts.daily.gov.GOV.txt /app/tmp/escrow_contacts.daily.gov.GOV.txt /app/tmp/escrow_domain_statuses.daily.gov.GOV.txt --debug docker compose run -T app ./manage.py load_transition_domain /app/tmp/escrow_domain_contacts.daily.gov.GOV.txt /app/tmp/escrow_contacts.daily.gov.GOV.txt /app/tmp/escrow_domain_statuses.daily.gov.GOV.txt --debug
``` ```
@ -239,7 +239,7 @@ Now that we've loaded all the data into TransitionDomain, we need to update the
In the same terminal as used in STEP 1, run the command below; In the same terminal as used in STEP 1, run the command below;
(This will parse the data in TransitionDomain and either create a corresponding Domain object, OR, if a corresponding Domain already exists, it will update that Domain with the incoming status. It will also create DomainInvitation objects for each user associated with the domain): (This will parse the data in TransitionDomain and either create a corresponding Domain object, OR, if a corresponding Domain already exists, it will update that Domain with the incoming status. It will also create DomainInvitation objects for each user associated with the domain):
(NOTE: If working in cloud.gov, remove "./manage.py" from the command) (NOTE: If working in cloud.gov, and remove "docker compose run -T app" from the command)
```shell ```shell
docker compose run -T app ./manage.py transfer_transition_domains_to_domains --debug docker compose run -T app ./manage.py transfer_transition_domains_to_domains --debug
``` ```
@ -256,7 +256,7 @@ Directs the script to load only the first 100 entries into the table. You can a
To send invitation emails for every transition domain in the transition domain table, execute the following command: To send invitation emails for every transition domain in the transition domain table, execute the following command:
(NOTE: If working in cloud.gov, remove "./manage.py" from the command) (NOTE: If working in cloud.gov, and remove "docker compose run -T app" from the command)
```shell ```shell
docker compose run -T app ./manage.py send_domain_invitations -s docker compose run -T app ./manage.py send_domain_invitations -s
``` ```
@ -269,7 +269,7 @@ This script's main function is to scan the transition domain and domain tables f
To analyze our database without running migrations, execute the script without any optional arguments: To analyze our database without running migrations, execute the script without any optional arguments:
(NOTE: If working in cloud.gov, remove "./manage.py" from the command) (NOTE: If working in cloud.gov, and remove "docker compose run -T app" from the command)
```shell ```shell
docker compose run -T app ./manage.py master_domain_migrations --debug docker compose run -T app ./manage.py master_domain_migrations --debug
``` ```
@ -278,7 +278,7 @@ docker compose run -T app ./manage.py master_domain_migrations --debug
To run the migrations again (all above migration steps) before analyzing, execute the following command (read the documentation on the terminal arguments below. Everything used by the migration scripts can also be passed into this script and will have the same effects). NOTE: --debug and --prompt allow you to step through the migration process and exit it after each step if you need to. It is recommended that you use these arguments when using the --runMigrations feature: To run the migrations again (all above migration steps) before analyzing, execute the following command (read the documentation on the terminal arguments below. Everything used by the migration scripts can also be passed into this script and will have the same effects). NOTE: --debug and --prompt allow you to step through the migration process and exit it after each step if you need to. It is recommended that you use these arguments when using the --runMigrations feature:
(NOTE: If working in cloud.gov, remove "./manage.py" from the command) (NOTE: If working in cloud.gov, and remove "docker compose run -T app" from the command)
```shell ```shell
docker compose run -T app ./manage.py master_domain_migrations --runMigrations --debug --prompt docker compose run -T app ./manage.py master_domain_migrations --runMigrations --debug --prompt
``` ```