- Send an POST request to
/auth/register - Set the content type to JSON
- Include in the request body a JSON object containing all the data you wish to save about your user
- required fields: "email" and "password"
- optional fields: currently just "name", but ask the back-end lead once those tasks are underway
Justin Richards magentanova
magentanova
/ leadScraper.py
Last active
August 8, 2016 16:20
Usage: `python leadScraper.py [cohortID1] [cohortID2] [etc...]`. Will scrape TIYA information on leads from each cohort and write to a csv. Be sure to fill in the `opts` under #configuration at the top of the script.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| import re | |
| import sys | |
| import csv | |
| import time | |
| import mechanize | |
| from bs4 import BeautifulSoup as BS | |
| # configuration | |
| opts = { | |
| 'email': '', |
magentanova
/ prog_report.rb
Last active
March 16, 2017 20:45
Scrapes newline to create progress reports for a given cohort. Gems to install: mechanize and pry. Also, you must edit the file to add your login credentials
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| require 'mechanize' | |
| require 'pry' | |
| $email = | |
| $password = | |
| $group_url = "https://online.theironyard.com/admin/groups/249" #example: 'https://online.theironyard.com/admin/groups/80' | |
| $path_url = "https://online.theironyard.com/admin/paths/930" #example: 'https://online.theironyard.com/admin/paths/333' | |
| def all_count |
magentanova
/ AUTH_README.md
Last active
March 30, 2017 20:04
Documentation for user authentication on IronPong and other Maestro-based apps
This document is a brief layout of the technology underlying Mountain Workshops, specifically as pertains to the production of mountainworkshops.org. It is intended as lay of the land for all participants and staff, not just developers, but some light technical descriptions will be provided as well as links to documentation for specific software. In general, Mountain Workshops involves a lot of different interlocking components and it's important for technologists and other stakeholders to get a bird's-eye view of what those components are, how they depend on each other, and how they are sequenced along the timeline of workshop.
The focus here is on the transmission of photojournalism stories. Videos are partially accommodated by this system. Great strides were made toward full automation in 2017, but as of now there are still manual steps that need to be taken for data visualization projects.
- This year's workshop and participants are created and saved as
magentanova
/ edit_site_readme.md
Last active
October 28, 2018 22:29
Instructions on editing mountainworkshops.org
Everything that you see on the site is editable through edit.mountainworkshops.org. Some parts of the interface will benefit from some explanation. For example:
This is probably the most complicated thing you might have to do, so it's the first and maybe only thing that we'll explain. It is unusual for someone to publish a fresh photojournalism story through the UI, since those are usually generated automatically on the last day of workshops. However there are cases, for example when a story was not ready to publish by midnight on that last day, when someone may need to publish the full story through the UI. So here are the steps: