Successfully reported this slideshow.

Days with Heroku

3,473 views

Published on

「Heroku-ja Meetup #1」のトーク
http://atnd.org/events/17223

Published in: Technology, Business
  • Be the first to comment

Days with Heroku

  1. 1. Days with Heroku @june29
  2. 2. Days with Heroku @june29
  3. 3. #rk11advent
  4. 4. #rk11advent
  5. 5. @june29
  6. 6. Days with Heroku @june29
  7. 7. Heroku and Me
  8. 8. Heroku and Me http://webos-goodies.jp/archives/51287729.html
  9. 9. Heroku and Me
  10. 10. Heroku and Me
  11. 11. Heroku and Me
  12. 12. My Apps http2irc presentation iReblog
  13. 13. Our Apps
  14. 14. Mehttp://www. ickr.com/photos/clothfairy/5893393187/
  15. 15. I’m Jun OHWADA
  16. 16. @june29
  17. 17. Days with Heroku @june29
  18. 18. Our Apps
  19. 19. Wanna5 / a 5. com / wa nn htt p:/
  20. 20. Our work ow (Staging)Developer Product Owner (Production)
  21. 21. Our work ow Feature Request (Staging)Developer Product Owner (Production) (1)
  22. 22. Our work ow Assignment (Staging)Developer Product Owner (Production) (2)
  23. 23. Our work ow Deploy (Staging)Developer Product Owner (Production) (3)
  24. 24. Our work ow Check (Staging)Developer Product Owner (Production) (4)
  25. 25. Our work ow Accept or Reject (Staging)Developer Product Owner (Production) (5)
  26. 26. Our work ow (Staging) Developer Product Owner Release CheckPush (Production) (6)
  27. 27. Our work ow (Staging)Developer Product Owner (Production)
  28. 28. Our work ow (Staging)Developer Product Owner New Feature Demo! (Production)
  29. 29. Our work ow (Staging)Developer Product Owner Deploy (Demo) New Feature Demo! (Production)
  30. 30. Our work ow (Staging)Developer Product Owner (Production)
  31. 31. Heroku brings (Staging)Developer Product Owner (Production)
  32. 32. Heroku brings (Staging)Developer Product Owner (Production)
  33. 33. Heroku bringsDeveloper Acceleration! (Staging) Product Owner (Production)
  34. 34. Heroku bringsDeveloper Acceleration! (Staging) Product Owner (Production)
  35. 35. Days with Heroku @june29
  36. 36. Practices
  37. 37. Practices - con g.yml $ heroku config:add KEY=VALUE
  38. 38. Practices - con g.yml case Notwife config_path = "config/config.yml" configatron.configure_from_yaml(config_path) if configatron.twitter.consumer_key.nil? configatron.twitter.consumer_key = ENV[TWITTER_CONSUMER_KEY] end if configatron.twitter.consumer_secret.nil? configatron.twitter.consumer_secret = ENV[TWITTER_CONSUMER_SECRET] end initializer script
  39. 39. Practices - con g.yml case Wanna5config_path = [config/config, ENV[SERVER_CONFIG], yml].compact.join(.)unless File.exists? config_path raise "Cant find config file: #{config_path}"endconfigatron.configure_from_yaml(config_path) initializer script
  40. 40. Our work ow (Staging)Developer Product Owner Deploy (Demo) New Feature Demo! (Production)
  41. 41. Practices - con g.yml $ heroku create demoapp $ heroku config:add SERVER_CONFIG=staging
  42. 42. PAAAAAAAAAAAAAAAAAAAS
  43. 43. Practices - con g.yml case Wanna5twitter: consumer_key: consumer_key consumer_secret: consumer_secretbasic_authentication: username: username password: password config.staging.yml
  44. 44. Practices - dyno case Wanna5
  45. 45. Practices - Add-ons case Wanna5
  46. 46. Days with Heroku @june29
  47. 47. Conclusion
  48. 48. @june29

×