Dependencies

None: The team member that takes on UCSBOrganization should start with this issue.

Overview

The team member that takes on UCSBOrganization as their database table should use this issue to track creating their personal dokku deployment.

[ ] An app named team02-YOURGITHUBID-dev is created on this team's dokku server, where YOURGITHUBID is your github id.
[ ] An database is configured for that app (see: https://ucsb-cs156.github.io/topics/dokku/postgres_database.html)
[ ] HTTPS is configured for that app (see: https://ucsb-cs156.github.io/topics/dokku/enabling_https.html)
[ ] The ADMIN_EMAILS are configured for that app.
- You should find the ones you need in a pinned post on your team's Slack channel.
- Instructions for configuring the variable are here: https://ucsb-cs156.github.io/topics/dokku/environment_variables.html
[ ] Google OAuth is configured for that app.
- Instructions for configuring OAuth credentials are here: https://ucsb-cs156.github.io/topics/oauth/oauth_google_setup.html
- Then you need to use the instructions here to configure the environment variables GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET: https://ucsb-cs156.github.io/topics/dokku/environment_variables.html
[ ] Everyone on the team, and the instructor and TAs, are all able to login with OAuth and see that they have admin privileges.
[ ] Initially, the main branch is deployed and works properly (later, you will deploy your own branches to this instance as you test them before merging.)

Next issue

Next, work on

Drag the issue for "UCSBOrganization - Create personal dokku dev deployment" directly into the "Done" column (we don't do code review on setup tasks like this one.)
Locate the issue: "Create database table for UCSBOrganization" on the Kanban board.
Assign that issue to yourself
Drag it into the "In Progress" column.
Start a new branch. The new branch name is something like xy-UCSBOrganization-create-db
```
git fetch
git checkout main
git pull origin main
git checkout -b your-branch-name
```
Start on the next issue