-
Notifications
You must be signed in to change notification settings - Fork 13
Developer Telecon #02 August 06 2015
Mike Dye edited this page Jan 4, 2017
·
1 revision
#Topics
- Discuss how portals and UAH system could interoperate.
- Portal could have a switch to automatically connect to UAH.
- Automatic exchange of data stream descriptions.
- Protocol for sending data to UAH.
- What minimum additional meta-data wold need to be configured in a portal?
- Simple "brochure" text description still needs to be written. We had discussed using the "User Experience" as source material for this.
Project Management
- Stakeholders
- Communication
- Use Cases
- Requirements
- Deliverables
- Milestones Associated with a Release
- "Sandbox" Milestones
- Github Workflow
AWS
- AWS Portal Migrations
- Amazon Appliance Workflow
- Overview
- Bringing up a new CHORDS Portal
- Cloud Formation
- EC2 Costing and Memory Constraints
Docker
- Running CHORDS
- Docker on AWS
- Duplicating Docker/Influxdb portals
- Docker on Raspberry Pi
- Docker Details and Tips
- Running CHORDS on Windows 10
Influxdb
Data Formats
Google Maps
Ingest Utilities
Miscellaneous
- Recovery from a full disk
- Github/Dockerhub release scheme
- CHORDS gh-pages and jeykll
- Bootstrap
- CHORDS Portal Web Site
- Dashboard Helper Refactor
- Development Notes
- Heroku
- Meteobridge
- Migrating from mysql to mysql/influxdb portals
- NCAR Wx Stations into CHORDS
- PAWS to CHORDS
- Post Get Query Syntax
- Postgres Testing
- Rails Tips
- Ruby and Rails Resources
- CUAHSI Archive
Historical Archive