[ ] 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.)
What to do next
Next:
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: "Copy files for Backend CRUD API UCSBOrganization from team02" 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-backend
git fetch
git checkout main
git pull origin main
git checkout -b your-branch-name
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.
Acceptance Criteria:
[ ] An app named
team03-YOURGITHUBID-dev
is created on this team's dokku server, whereYOURGITHUBID
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.
[ ] Google OAuth is configured for that app.
GOOGLE_CLIENT_ID
andGOOGLE_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.)What to do next
Next:
UCSBOrganization
from team02" on the Kanban board.xy-UCSBOrganization-backend