Releases: cloudfoundry-community/autosleep
v1.0.0
What it does
- Automatically bind applications according to parameters given at service instance creation
- Watch bound application activities
- Stop them when idle duration is reached
- Restart them on incoming web traffic
How to deploy
See README for more information on how to deploy
⚠️ WARNING
This version should be installed as a fresh new one. Updating from a previous version won't work w.r.t. to the mysql db content. (We promise to be more retro-compatible for next releases)
v0.2.2
What it does
- Automaticaly bind applications according to parameters given at service instance creation
- Watch bound application activities
- Stop them when idle duration is reached
How to deploy
See README to kown how to fill the manifest.tmpl.yml
file
cf push -f manifest.yml -p org.cloudfoundry.autosleep-0.2.1.war
Modifications:
- Rename
ApplicationBinding
toBinding
(:warning: Impact database) - reactor dependancy is stored localy
v0.2.1
What it does
- Automaticaly bind applications according to parameters given at service instance creation
- Watch bound application activities
- Stop them when idle duration is reached
How to deploy
See README to kown how to fill the manifest.tmpl.yml
file
cf push -f manifest.yml -p org.cloudfoundry.autosleep-0.2.1.war
This version fixes the issue mentionned in #143 when user create a service instance without parameters
v0.2.0
What it does
- Automaticaly bind applications according to parameters given at service instance creation
- Watch bound application activities
- Stop them when idle duration is reached
How to deploy
See README to kown how to fill the manifest.tmpl.yml
file
cf push -f manifest.yml -p org.cloudfoundry.autosleep-0.2.0.war
v0.1.0
First version:
What it does
For now, manually bound applications will be stopped when no recent restart or logs.
How to deploy
First edit the manifest.tmpl.yml file with the appropriate values.
Then
cf push -f manifest.yml -p org.cloudfoundry.autosleep-0.1.0.war