# Development cycle for Ray + Serve

**URL:** <https://discuss.ray.io/t/development-cycle-for-ray-serve/6469>\
**Category:** Ray Serve\
**Created:** [June 10, 2022, 9:25pm UTC](https://discuss.ray.io/t/development-cycle-for-ray-serve/6469 "2022-06-10T21:25:25Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Henry\_Thornton](https://avatars.discourse-cdn.com/v4/letter/h/8491ac/32.png) [@Henry\_Thornton](https://discuss.ray.io/u/Henry_Thornton)\
**Post date:** [June 10, 2022, 9:25pm UTC](https://discuss.ray.io/t/development-cycle-for-ray-serve/6469/1 "2022-06-10T21:25:25Z")

</div>

As auto-reload is not yet available, my ray+serve development cycle is

edit-code  
start-ray  
run-code  
debug  
edit-code  
stop-ray  
start-ray  
run-code  
etc

Is there a better way to get away from the start-ray … stop-ray cycle until auto-reload appears? Thanks

---

<div class="post-metadata">

**Author:** ![architkulkarni](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ray.io/architkulkarni/32/10_2.png) [@architkulkarni](https://discuss.ray.io/u/architkulkarni)\
**Post date:** [June 13, 2022, 4:59pm UTC](https://discuss.ray.io/t/development-cycle-for-ray-serve/6469/2 "2022-06-13T16:59:34Z")

</div>

Hi @Henry_Thornton, another option is to edit the code in your Deployment and then redeploy by calling `.deploy()` again, which will replace all replicas of the old version with the new version. This way you don’t have to restart the Ray cluster.