allard
51 lines
2.2 KiB
Markdown
51 lines
2.2 KiB
Markdown
user : admin
|
||
password: Defectdojo01@
|
||
|
||
|
||
======
|
||
|
||
migratie
|
||
|
||
- inloggen in de uwsgi container en dan:
|
||
- python manage.py migrate
|
||
|
||
|
||
toevoegen environment:
|
||
|
||
https://defectdojo-dev.allarddcs.nl/admin/dojo/development_environment/
|
||
|
||
#postgres schema update
|
||
als schema achterloopt:
|
||
|
||
dan:
|
||
|
||
kubectl exec -it uwsgi-6cc455bb57-5v4sk -n defectdojo -- /bin/bash
|
||
defectdojo@uwsgi-6cc455bb57-5v4sk:/app$ python manage.py migrate
|
||
[05/Feb/2026 20:14:19] INFO [dojo.auditlog:164] Registering models with django-pghistory
|
||
[05/Feb/2026 20:14:19] INFO [dojo.auditlog:381] Successfully registered models with django-pghistory
|
||
[05/Feb/2026 20:14:19] INFO [dojo.auditlog:443] Audit logging disabled
|
||
Operations to perform:
|
||
Apply all migrations: admin, auditlog, auth, authtoken, contenttypes, django_celery_results, dojo, pghistory, sessions, single_session, sites, social_django, watson
|
||
Running migrations:
|
||
Applying dojo.0247_remove_finding_insert_insert_and_more... OK
|
||
Applying dojo.0248_alter_general_survey_expiration... OK
|
||
Applying dojo.0249_findingreviewers_findingreviewersevent_and_more... OK
|
||
Applying dojo.0250_pghistory_backfill...[05/Feb/2026 20:14:42] INFO [dojo.db_migrations.0250_pghistory_backfill:26] pghistory is not enabled. Skipping backfill.
|
||
OK
|
||
Applying dojo.0251_usercontactinfo_reset_timestamps... OK
|
||
Applying dojo.0252_finding_template_changes... OK
|
||
Applying dojo.0253_migrate_vulnerability_ids_to_textfield... OK
|
||
Applying dojo.0254_remove_vulnerability_id_template_model... OK
|
||
Applying dojo.0255_remove_system_settings_product_grade... OK
|
||
|
||
#password resetten:
|
||
kubectl exec -it uwsgi-6cc455bb57-5v4sk -n defectdojo -- /bin/bash
|
||
python manage.py changepassword admin
|
||
|
||
|
||
Yes — you can safely leave HTTP_AUTH_PASSWORD (or any similar admin/password env var) out of the YAML from now on, as long as:
|
||
1. You’ve already set the admin password in the database (via python manage.py changepassword admin or the initializer).
|
||
2. You don’t need to automatically create/reset the password on pod startup.
|
||
|
||
The YAML variable only has an effect during first-time initialization of the app — it does not override the DB once the admin user exists. So leaving it out won’t break anything.
|