Mathis/allianceauth
1
0
Fork 0
mirror of https://gitlab.com/allianceauth/allianceauth.git synced 2025-07-09 20:40:17 +02:00
Code Issues Packages Projects Releases Wiki Activity

minor fixes to dev environment setup

Browse Source
This commit is contained in:
Arc Tiru 2022-09-07 11:00:38 -07:00
parent 8d255fb720
commit cf20100cb5
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/development/dev_setup/aa-dev-setup-wsl-vsc-v2.md
View File

@ -284,7 +284,7 @@ python manage.py migrate
We also need to create a superuser for our AA installation: We also need to create a superuser for our AA installation:
```bash ```bash
python /home/allianceserver/myauth/manage.py createsuperuser python manage.py createsuperuser
``` ```
## Running Alliance Auth ## Running Alliance Auth
@ -319,7 +319,7 @@ In addition you can start a celery worker instance for myauth. For development p
This can be done from the command line with the following command in the myauth folder (where manage.py is located): This can be done from the command line with the following command in the myauth folder (where manage.py is located):
```bash ```bash
celery -E -A myauth worker -l info -P solo celery -A myauth worker -l info -P solo
``` ```
Same as AA itself you can start Celery from any terminal session, from a terminal window within VSC or as a debug config in VSC (see chapter about debugging for details). For convenience we recommend starting Celery as debug config. Same as AA itself you can start Celery from any terminal session, from a terminal window within VSC or as a debug config in VSC (see chapter about debugging for details). For convenience we recommend starting Celery as debug config.