Move VRFY Core Functionality Into Its Own Django-App - Githubissues

reed-college / vrfy

the (bare bones) beginnings of the cs hw project for the sds

0 stars 1 forks source link

Move VRFY Core Functionality Into Its Own Django-App #20

Open gmcquillan opened 8 years ago

gmcquillan commented 8 years ago

Having a Django installation be public is pretty problematic for a couple of reasons:

Sharing unnecessary configuration data, which might confuse other users of the system if their operational concerns are different.
Sharing secret configuration data which should not be public.

Proposal in two parts:

Break all of the Vrfy application logic up into its own Django-App. This will be the public repository that is shared with other institutions, and contains no configuration data of its own, besides defaults.
Create a private repository that contains your actual installation of Vrfy, registering the public Vrfy django-app in its settings.py

Documentation describing how DjangoApps work: https://docs.djangoproject.com/en/1.9/intro/reusable-apps/

gmcquillan commented 8 years ago

This is another good resource that covers how the security infrastructure of Django works: https://docs.djangoproject.com/en/1.9/topics/security/