# How to upgrade if \`/var/discourse\` has only \`shared\` and is not git repo

**URL:** <https://meta.discourse.org/t/how-to-upgrade-if-var-discourse-has-only-shared-and-is-not-git-repo/157982>\
**Category:** Product Support\
**Created:** [16 ביולי,‏ 2020,‏ 9:50pm UTC](https://meta.discourse.org/t/how-to-upgrade-if-var-discourse-has-only-shared-and-is-not-git-repo/157982 "2020-07-16T21:50:41Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![ulysses4ever](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ulysses4ever/32/122522_2.png) [@ulysses4ever](https://meta.discourse.org/u/ulysses4ever)\
**Post date:** [17 ביולי,‏ 2020,‏ 1:03am UTC](https://meta.discourse.org/t/how-to-upgrade-if-var-discourse-has-only-shared-and-is-not-git-repo/157982/6 "2020-07-17T01:03:56Z")

</div>

> [@Stephen](#):
>
> it’s either a very very old installation

This is indeed most likely what’s going on. It’s running Discourse 2.1.0 (if it makes things clearer).

> [@Stephen](#):
>
> A new VM means a new virtual server, assuming your instance isn’t on dedicated hardware.

That’s the thing: my instance IS on dedicated hardware.

> [@pfaffman](#):
>
> You do this: [Install Discourse in production with the official supported instructions](https://meta.discourse.org/t/discourse-official-standard-installation/142537)

So, I understand currently no Docker involved. At least, not manually. At least, it’s good to know that there is just one way to set it up and it uses just `git clone` and the setup script.

What bothers me is how I would gently scrap the old version, given that everything is happening on an actual physical machine (i.e. nothing “virtual”). I did the backup, that’s easy. Now what?

---

_[View the full topic](https://meta.discourse.org/t/how-to-upgrade-if-var-discourse-has-only-shared-and-is-not-git-repo/157982)._
