Badges App

gistfile1.txt

- Django App Implemented by 3rd party served by us
- Part of the Saudi Deliverable
- Does it have a database? Yes
-- Postgres?

-- Basic service
--- What version of django?
---- 1.7
--- Do people already log into this app?
--- Does it have special CORS considerations?
---- No
--- Will need email it looks like
---- SES setup?
---- What domain should it send e-mail from.
---- We may need a seperate AWS account for this.
--- What domain?
---- Need one that is not under edx.org?  Beth and Ned to talk.
---- Start with badges.edx.org for now
----- Can use wildcard cert for SSL for this.
-- Completely independent of the edx-platform
-- How often will it be updated?
--- Updates every 2 weeks or so
--- Unknown


-- How does the DB scale?

-- Who is the engineering owner of badges? Beth and Ned to talk.
--- Who will keep track of requirement/security updates
--- Code updates
--- Unknown

-- We'll need a staging version of this service.


-- Who is reviewing the code?
-- We need to add it to the motasano security review.

-- Image per badge per user


NOTES FOR MEETING WITH NATE
---------------------------

- We need a health endpoint('/health') so that load-balancers can know when the endpoint is healthy.
- We need to be able to drop settings using our current setup if possible.  Need a production settings file which picks up overrides from a file on disk.