> For the complete documentation index, see [llms.txt](https://revdebug.gitbook.io/revdebug/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://revdebug.gitbook.io/revdebug/updating-revdebug-server.md).

# Updating RevDeBug server

When you have installed RevDeBug server using [Installing RevDeBug server](/revdebug/installing-revdebug-server.md) guide, updating it requires only three actions (all commands need to be executed in the cloned docker-compose project directory):

{% tabs %}
{% tab title="Default" %}

* Stopping RevDeBug server containers prior to upgrading:\
  `sudo docker compose -p revdebug down`
* Pulling new version of compose file from the git repository:\
  `git pull`
* Pull new versions of docker images:\
  `sudo docker compose -p revdebug pull`
* Starting new version of RevDeBug server containers:\
  `sudo docker compose -p revdebug up -d`
  {% endtab %}

{% tab title="Standalone" %}

* Stopping RevDeBug server containers prior to upgrading:\
  `sudo docker-compose -p revdebug down`
* Pulling new version of compose file from git repository:\
  `git pull`
* Pull new versions of docker images:\
  `sudo docker-compose -p revdebug pull`
* Starting new version of RevDeBug server containers:\
  `sudo docker-compose -p revdebug up -d`
  {% endtab %}
  {% endtabs %}

After confirming new version of RevDeBug server started, you may clean up old container images by executing: `sudo docker system prune`