New local environment directions

[okaycj]

Here are the new Django local environment instructions.

[becky-gilbert]

@okaycj FYI I haven't forgotten about reviewing this - I'm just putting together my own notes on the installation process and then will cross-reference those with what you have here. Might take a few days since I'm still consolidating new info and getting interrupted with other things.

[becky-gilbert]

In this section maybe we should add:

• Install homebrew (or does in not matter which package manager someone is using?). Maybe we could suggest homebrew, and then also suggest brew install mkcert in parentheses for the next step.
• Install git, and make sure that ssh keys are set up (for step 1): https://docs.github.com/en/authentication/connecting-to-github-with-ssh (this was an issue for both me and Melissa: UPDATE - Developer environment setup #230)

[becky-gilbert]

Some commands (like this one, I think) generate a lot of output in the terminal. It might be helpful to add screenshots or text blocks showing this output and what it should look like if it has finished successfully. (If you agree then we could add this later, if you don't want to do it for this PR.)

[becky-gilbert]

Suggested change

	At this point, the services should all be up and running. Direct your browser to https://localhost:8000 to see the local environment. In the future, to start the services you will only need to run "make serve"
	At this point, the services should all be up and running. Direct your browser to https://localhost:8000 to see the local environment. In the future, to start the services you will only need to run `make serve`. You will need to keep the terminal window/tab open while using your local server. You can stop the server with COMMAND/CTRL+C or by closing the terminal.

[becky-gilbert]

And this might be another place to add a screenshot or gif of the browser at localhost:8000.

[becky-gilbert]

When I first read through this, I thought this and subsequent sections were still part of the initial set-up. So could we make that distinction clearer by replacing the Django heading here with something like "Useful Commands", and then nested under that put subheadings for "Django", "Rabbitmq", "Postgres", "Authentication" and "Handling Video"?

I also think it would be helpful to have a short introductory sentence at the start of each of these subsections, indicating what this part of the system does. E.g. for Django: "This is the Python-based web framework that is used to create the Lookit website (everything except for running the studies themselves)", for Postgres: "This is the database that stores information that the Lookit website needs, such as user accounts, study information <etc.>". This might be helpful for users who encounter some kind of problem after initial set up but don't know which framework/service to focus on.

[becky-gilbert]

Might be useful to say what the Celery worker error looks like, e.g. with a screenshot or text.

[becky-gilbert]

This section says "you will need to log in using the superuser you created earlier using manage.py", which I think is referencing make superuser on line 104, but I don't see any references to "manage.py" on this page, so that might be confusing. Is that left over from an earlier version?

[becky-gilbert]

(This applies to the start of the Handling Video section, I'm just not able to comment in the right place...)
I think it would be helpful to explain in simpler terms when this step is needed. E.g.
"You will be able to run internal Lookit studies through your development server, but this additional step is needed if you want to generate and save video recordings. The project includes an incoming webhook handler...".