# Easy (not better) way to update Trellis

**URL:** https://discourse.roots.io/t/easy-not-better-way-to-update-trellis/7207
**Category:** trellis
**Created:** 2016-07-16T16:16:14Z
**Posts:** 3
**Showing post:** 3 of 3

## Post 3 by @aitor — 2016-07-17T06:03:21Z

Thank you for response. I’ve added “rebase” to my learning list. For now, I tried the update by hand, succesfully. This was my workflow:

1. **Clone trellis** and rename it as ansible

2. **Update ansible** : `sudo pip install ansible==2.0.2.0` (Warning: without “2.0.2.0” doesn’t work because ansible 2.1.0.0 will be installed)

3. **Update all group\_vars** one by one (there is a lot of new default variables that is no needed now). Be carefull, if db\_name doesn’t match with default db\_name, it must be specified, in order to not loss data of existing projects at remote server.

4. **Provision development environment** : `vagrant up —-provision` (this generate a new VB machine, it is a bad way)

5. **Update** `hosts/*`

6. **Update** `deploy-hooks/*`

Now I can provision server and deploy old projects without losing data.

---

_[View the full topic](https://discourse.roots.io/t/easy-not-better-way-to-update-trellis/7207)._