Re: Diff between cf restart and cf restage


Cornelia Davis <cdavis@...>
 

The staging process has access to env variables, etc. so the env can affect
the contents of the droplet.

You might notice that when you do a cf set-env you get a message that
advises you to do a cf restage. Because CF doesn't know whether your
buildpack is affected by env changes, it recommends the more extreme option.

For some (many) apps, a cf restart would be sufficient.

On Tue, Nov 3, 2015 at 9:15 PM, Matthew Sykes <matthew.sykes(a)gmail.com>
wrote:

`restage` will stop your application, run the application bits through the
staging process to create a new droplet, and then start the new droplet.
It's a lot like `push` but without actually pushing new application bits.

`restart` will simply stop your application and start it with the existing
droplet.

You typically restart when you need your applicaiton's environment
refreshed and you typically restage when you need/want the buildpack to run
without updating the application source.

Hope that helps.

On Tue, Nov 3, 2015 at 2:46 PM, Nikhil Katre <nikhil.katre(a)appdynamics.com
wrote:
Hi,

Can someone explain in detail what is the difference between cf restart
and cf restage ?

--
Thanks,

*Nikhil Katre* | Software Engineer
Mobile: (919) 633 3940 <%28303%29%20946%209911>

AppDynamics
The Application Intelligence Company
Watch <http://appdynamics.wistia.com/medias/56gnkuk6mv>our Video | Try
<https://portal.appdynamics.com/account/signup/signupForm>our FREE Trial
| Twitter <http://www.twitter.com/appdynamics>| Facebook
<http://www.facebook.com/pages/AppDynamics/193264136815?ref=nf>|
appdynamics.com <http://www.appdynamics.com/>


--
Matthew Sykes
matthew.sykes(a)gmail.com

Join cf-dev@lists.cloudfoundry.org to automatically receive all group messages.