# Creating a duplicate of production environment

**URL:** <https://meta.discourse.org/t/creating-a-duplicate-of-production-environment/61966>\
**Category:** Self-hosting\
**Created:** [2 mei 2017 om 15:38 UTC](https://meta.discourse.org/t/creating-a-duplicate-of-production-environment/61966 "2017-05-02T15:38:05Z")\
**Posts on this page:** 1\
**Showing post:** 24

<div class="post-metadata">

**Author:** ![TallTrees](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/talltrees/32/208620_2.png) [@TallTrees](https://meta.discourse.org/u/TallTrees)\
**Post date:** [24 januari 2021 om 05:28 UTC](https://meta.discourse.org/t/creating-a-duplicate-of-production-environment/61966/24 "2021-01-24T05:28:28Z")

</div>

> [@Henti\_Smith](#):
>
> `# If you need a specific commit, do:`  
> `# git reset --hard git_commit_hash_goes_here`

Confusingly I’m getting the following error here:

```
$ git reset --hard '28032eaf38530b96c92aef3df42841aa8613a2f6'
fatal: Could not parse object '28032eaf38530b96c92aef3df42841aa8613a2f6'.

```

I believe that’s the right hash that’s running on my production server, and it looks to exist on github: [Commits · discourse/discourse · GitHub](https://github.com/discourse/discourse/commits/28032eaf38530b96c92aef3df42841aa8613a2f6)

Looks clean otherwise:

```
$ git status
# On branch master
nothing to commit, working directory clean
$ git fsck
Checking object directories: 100% (256/256), done.
Checking objects: 100% (5038/5038), done.

```

I’m wanting to stage the upgrade to 2.7.0.beta2, but this looks to be preventing me from starting at the same point as the production servers ☹

---

_[View the full topic](https://meta.discourse.org/t/creating-a-duplicate-of-production-environment/61966)._
