{"push_id":1353904691,"size":1,"distinct_size":1,"ref":"refs/heads/vagrant-update","head":"3662022ec8cf569559d445029dc731030af8f826","before":"71e544c20548daffa37f818bfabf15efd83b9117","commits":[{"sha":"3662022ec8cf569559d445029dc731030af8f826","author":{"name":"Mason Donahue","email":"d545ac7f1ba33eff1754eb3bb5b87e38d8a0b7fb@gmail.com"},"message":"Switch to using python-dotenv\n\nIdeological discussions about 12-factor apps aside, we currently have\ntwo deployment-specific secrets (DB URI and CSRF token) and we're\nassuredly going to add more later. We need a way of managing those that\nisn't \"creating and managing a new file with secrets\" or \"stuffing them\nin the global environment\".\n\nEnter dotenv. This python module lets you specify things in a file\ncalled .env that then get added to the os.environ namespace. This is\nhandy because instead of deployment requiring hand-hacking of the\nprocess environment, it just lives with the app. It's also a good\nstarting point if future users of OO don't want to janitor their own\nservers: heroku, for instance, mostly works through .env files.\n\nThis change did some reworking to the app itself that we should test out\nbefore sending to prod; it also changes the provisioning of the vagrant\nVM to properly plop the right thing into .env. Now the app starts and\nruns with sample data automatically in a vagrant. I also made the\ncreate_db.py script idempotent-ish, so it doesn't do anything if it\nreceives a DatabaseAlreadyControlledError.\n\nI've also updated the dev and deploy documentation to reflect our wonderful\nNew Reality.","distinct":true,"url":"https://api.github.com/repos/lucyparsons/OpenOversight/commits/3662022ec8cf569559d445029dc731030af8f826"}]}
{"actor":{"display_login":"r4v5"}}