Skip to content

Commit

Permalink
Fix step order
Browse files Browse the repository at this point in the history
  • Loading branch information
chiatt committed Sep 28, 2024
1 parent 7d4a737 commit 24814b4
Showing 1 changed file with 7 additions and 7 deletions.
14 changes: 7 additions & 7 deletions releases/7.6.0.md
Original file line number Diff line number Diff line change
Expand Up @@ -449,7 +449,7 @@ Minor incompatibilities:
)
```

12. Update urls.py:
11. Update urls.py:
```
from django.conf import settings
from django.conf.urls.static import static
Expand All @@ -475,7 +475,7 @@ Minor incompatibilities:
urlpatterns.append(path("i18n/", include("django.conf.urls.i18n")))
```

13. If you have updated `templates/javascript.htm` in your project with any project-level urls, they must be moved to `templates/arches_urls.htm`. All other updates to `templates/javascript.htm` should remain in-place. eg:
12. If you have updated `templates/javascript.htm` in your project with any project-level urls, they must be moved to `templates/arches_urls.htm`. All other updates to `templates/javascript.htm` should remain in-place. eg:
```
<!-- my_project/templates/javascript.htm -->
Expand Down Expand Up @@ -552,22 +552,22 @@ Minor incompatibilities:
- If you had values other than ``None`` in ``MIN_ARCHES_VERSION`` and ``MAX_ARCHES_VERSION`` in settings.py, update the core arches dependency in the `dependencies` block of `pyproject.toml`.


17. If you do any custom development, update and reinstall the python development dependencies, and install the pre-commit hooks. (You can always ignore these hooks with `git commit --no-verify`.)
16. If you do any custom development, update and reinstall the python development dependencies, and install the pre-commit hooks. (You can always ignore these hooks with `git commit --no-verify`.)

1. Navigate to the directory with your project's .pre-commit-config.yaml file.
```
pip install -e '.[dev]'
pre-commit install
```

18. Navigate to the directory with your project's package.json file. Then run:
17. Navigate to the directory with your project's package.json file. Then run:
```
npm install
```

19. Start your application server in a separate terminal if it's not already running.
18. Start your application server in a separate terminal if it's not already running.

20. In the same terminal window where you ran `npm` ( on the same level as `package.json` ):
19. In the same terminal window where you ran `npm` ( on the same level as `package.json` ):

1. Run `npm run gettext:extract` followed by `npm run gettext:compile`. This will generate i18n files in your `locale` directory. Even if you're
not planning on internationalizing your project, it's important to have these files for creating Vue components.
Expand All @@ -578,7 +578,7 @@ Minor incompatibilities:
- `npm run build_development` will build a development bundle for the frontend assests of the application -- this should complete in less than 2 minutes
- If running your project in production:
- `npm run build_production` This builds a production bundle. **takes up to 2hrs depending on resources**
- Alternatively you can run `python manage.py build_production`. This will create a production bundle of frontend assessts and also call `collectstatic`.
- Alternatively you can run `python manage.py build_production`. This will create a production bundle of frontend assets and also call `collectstatic`.

20. Test your project with deprecation warnings enabled.

Expand Down

0 comments on commit 24814b4

Please sign in to comment.