Docker setup - missing step

[Big-Vi]

Hello,

I was trying to set up the WagTail Demo locally and using the specified commands did setup my environment. But it didn't allow me to log in to the backend(authentication error) until I ran the below command.

docker-compose run app /venv/bin/python manage.py createsuperuser

Can I create a pull request by changing the instruction?

Cheers V

[zerolab]

Hey @Big-Vi,

Have you seen the

Log into the admin with the credentials admin / changeme.

line in the README? did it not work for you?

[Big-Vi]

The below credentials did not work for me. username: admin password: changeme

[cmuc24]

same, credentials from the docs are without any function

creating superuser solved it docker-compose run app /venv/bin/python manage.py createsuperuser

thanks @Big-Vi

[bc6really]

I agree with @cmuc24, thanks @Big-Vi. I should also note that the hosted demo site is having a similar issue; when asked for the username and password, admin / changeme does not work.

[gasman]

I think the issue with the hosted demo site is different - since there's a single database shared across all users, it's easy for anyone to casually change the default login (and they may well even think it's the right thing to do, because the password is "changeme" after all).

I'm not sure why the extra createsuperuser step would be necessary here, because the admin / changeme account is hard-coded in the fixture along with the rest of the site data - if that account was missing, then the rest of the demo data would be missing too. We've previously had issues with the Docker setup due to the fact that the webserver setup and the database setup happen in parallel, so it's possible for the webserver to become available before the data is fully loaded - but again, if that was the problem here, you wouldn't see the bakery homepage either at that point (only the default "Welcome to your new Wagtail site" splash page).

[mllabs]

I was also having trouble with logging in to either the docker container or the demo site. The 'fix' does allow me to log in, but none of the data is there, so I figured it's probably due to the database not being up when the initial data load was running as mentioned by @gasman above.

Anyway - to fix both issues, I ran the command:

docker-compose run app /venv/bin/python manage.py load_initial_data

This fixed the login issue as well as the missing content.

[gasman]

Have confirmed that the current instructions do work, but you have to wait several seconds after docker compose up --build -d for the database initialisation to complete before running the load_initial_data command. Instructions updated accordingly in 274bba12799335665372e9ca5a05e4cdd0d43797.