(also removed the sample app, as it lives in the tests repo) Change-Id: I5cdf9995584f20c4df38877840c400899e86a451
…logs list Change-Id: Icda59fbff2629f6afb6d5fd8cd25c28e23b9f92a
Why app startup, and not part of staging? Because every deployment related tasks are appened to the 'startup' script, so they'll be run on the DEA (before app startup) instead of the cloud_controller. Not sure if this should change. Change-Id: I1b1f09fb7965d318f522a28c165d17e355ea195f
* use virtualenv's pip, not global one (which requires sudo anyway) * redirect pip's output to pip.log, otherwise it is impossible to tell what went wrong when pip fails Change-Id: Idba6bc42e699d09a77b446c0c4ed7c3200857df9
…ks/runtimes around that are no longer in the DB - Added started apps and instances - Aggregated queries to reduce number of requests"
For applying this fix, you can use MySQL (/w em_mysql2 adapter) as cloud controller database by configuring cloud_controller.yml as follows: development: database: cloudcontroller host: localhost port: 3306 username: root password: password adapter: em_mysql2 encoding: utf8 timeout: 2000 Change-Id: Ie881f617f77d1d4aacc0772b1594547b9beb1af5
Setting a default value for REVISION was incorrect. nil is the right default for this property. Change-Id: Iaf2d636cb508c4e3469f479663f9ade8ecf9f895