docs: remove mention of deprecated env variables

Author: jgravois

docs/guides/getting-started.md

@@ -128,11 +128,11 @@ Compiler developers, be sure to follow the instructions in the [Django Admin upd
 
 If you have a need to maintain some test data that you've added via the Django Admin across multiple development sessions:
 
-1. Set `DJANGO_DB_RESET=false` in your `.env` file
 1. Create a new set of temporary fixtures:
    ```bash
    python manage.py dumpdata --indent 2 --output benefits/core/migrations/temp_fixtures.json
    ```
+
    - It's important that the filename end in `fixtures.json` so that it's ignored by Git.
 1. Set `DJANGO_DB_FIXTURES` to the path of the new file you just created in `.env`
 1. Rebuild the devcontainer

docs/guides/postgresql.md

@@ -21,10 +21,10 @@ To manage backups, use the app container's `web-storage` mounted volume.
 
 ```bash
 # copy a backup into the mounted volume
-cp db_data.json /home/calitp/app/data/db_data_YYY_MM_DD.json
+cp /calitp/app/db_data.json /calitp/app/data/db_data_YYY_MM_DD.json
 
 # copy a backup from the mounted volume
-cp /home/calitp/app/data/db_data_YYY_MM_DD.json db_data.json
+cp /calitp/app/data/db_data_YYY_MM_DD.json /calitp/app/db_data.json
 ```
 
 You can view the files in the mounted volume (and upload new ones) by navigating to Azure > Storage account > Data storage > Classic file shares > `web-storage` > Browse.

docs/guides/troubleshooting.md

@@ -75,13 +75,4 @@ A common problem that causes Littlepay API failures is that the certificate expi
 
 ### Eligibility Server
 
-If the Benefits application gets a 403 error when trying to make API calls to the [Eligibility Server](https://docs.calitp.org/eligibility-server/), it may be because the outbound IP addresses changed, and the Eligibility Server firewall is still restricting access to the old IP ranges.
-
-1. Grab the `outbound_ip_ranges` `output` values from the most recent Benefit [deployment](https://calenterprise.visualstudio.com/CDT.OET.CAL-ITP/_build?definitionId=828) to the relevant environment.
-1. Update the IP ranges
-   1. Go to the [Eligibility Server Pipeline](https://dev.azure.com/mstransit/courtesy-cards/_build?definitionId=1&_a=summary)
-   1. Click `Edit`
-   1. Click `Variables`
-   1. Update the relevant variable with the new list of CIDRs
-
-Note there is nightly downtime as the Eligibility Server restarts and loads new data.
+Note there is nightly downtime as the [Eligibility Servers](https://docs.calitp.org/eligibility-server/) restart and load new data.

docs/reference/environment-variables.md

@@ -197,30 +197,6 @@ Boolean:
 - `true`: the `DATABASES` Django setting is configured to use Postgres (see [`Django database (Postgres)`](#django-database-postgresql))
 - `false` (default): the `DATABASES` Django setting is configured to use SQLite (see [`Django database (SQLite)`](#django-database-sqlite))
 
-## Django database (SQLite)
-
-### `DJANGO_DB_FILE`
-
-!!! info "Local configuration"
-
-    This setting only affects the app running on localhost
-
-The name of the Django database file to use locally (during both normal app startup and for resetting the database).
-
-By default, `django.db`.
-
-### `DJANGO_DB_RESET`
-
-!!! info "Local configuration"
-
-    This setting only affects the app running on localhost
-
-Boolean:
-
-- `true`: deletes the existing database file and runs fresh Django migrations.
-- `false` (default): Django uses the existing database file.
-  (Note: Fixtures will still be loaded, updating any values on those objects if they have changed.)
-
 ## Django database (PostgreSQL)
 
 ### `DJANGO_DB_NAME`