- Form to add new projects - https://airtable.com/shrPNzCqzHNpaXadS
- Heroku project https://dashboard.heroku.com/apps/projects-registry
- Projects registry in AirTable - Link for Editors & Admins
- AirTable table with Form
- Heroku account with access to project
- Git on local computer
- Jira Software space with tempalte projects. NB Only issue tree is copied to new projects
- GitHub account for repos
- Python knowledge + libraries listed in requirements.txt and runtime.txt in repo
Simple way is
- Only once - Install Heroku Cli (instructions for Win/Mac here)
- Once in a while - do
heroku login, continue in browser - do
heroku git:clone -a projects-registry - enter folder by
cd projects-registry
When done editing, git add, then git commit, then git push heroku, app will be deployed, rebuilt and launched
Config variables are managed in project settings on Heroku, click [Reveal Config Vars].
NB After editing any of the variables, container will restart taking the changes into account, last codebase will be used.
- AIRTABLE_BASE: App Id, go to AirTable Help -> API, select desired database and ID will be shown
- AIRTABLE_KEY: Generate API key here
- AIRTABLE_TABLE: Same as App (Base) Id above, just with Table
- CC_TEMPL: Chose cookiecutter template for repos, currently Data Science
- GIT_TOKEN: Github token generated here, requires
repopermissions - GIT_U: GitHub username
- JIRA_EMAIL: Self-explanatory, account requires
adminpermissions for space - JIRA_SRV: Self-explanatory, https://rob-sandberg.atlassian.net
- JIRA_TEMPL: possible values are listed in Jira API docs
- JIRA_TOKEN: Generate in account settings -> security
- LOGGING: TRACE (detailed) or DEBUG (medium) or INFO (superficial)
- SACRED: List of templates-projects' keys, currently only MIG for Migration project, separated by semicolon
- TZ: e.g. America/Denver, internal instance timezone. Heroku logs are always UTC