You have an app running locally that lets people explore data. Great. How will anyone find it, though? You can't serve this off your laptop.
And if they do happen to find your app running on your laptop somehow, your localhost don't scale!
We'll also cover basic terminology and concepts.
- Devops
- Sysops
- Secops/infosec
- Typical day
- Launch day
- Doomsday
See the GitHub for Journalism material.
- What does "deploying an app" mean? Explainer TK.
- Intro to VirtualBox, vagrant, docker, salt and other provisioning tools:
- How they work together
- What to use and why
- Host static site on GitHub
- Host static site on S3
- Local env setup with Vagrant for one lang
- Single-server Heroku hello worlds for Node, Sinatra, Rails, Flask, Django, Clojure
- Single server Heroku with databases of your choosing
- Scheduled releases
- Continuous deployment
Things you can monitor:
- system load/CPU/memory with things like monit, upstart
- services (nginx, MySQL, etc) again with monit, upstart or similar
- apps (memory usage, exceptions)
- response times (internal or external ways like pingdom)
- manual vs auto
- horizontal (throw more machines at it)
- optimization
- in memory
- persistent
- headers
- template or data fragments, entire pages
- database / inc redis
- filesystem
- 2 hard problems
- busting
- w/o causing pile up
- local
- in app
- in request like http headers
- external like varnish
- layers to cache on and what to cache at each
- Deploy PANDA on EC2
- Two-server Heroku with manual deployments and data migrations
- Two-server Heroku with CI from master and stable branches
- Add caching and CDN
- Deploy app on VPS via Salt+Docker
- Election 2012
- Sochi 2014
- SEA
? Walk through an active deployment to look at logs and analytics then create new stack and move app ?