# Understanding theme blob assets behavior

**URL:** <https://meta.discourse.org/t/understanding-theme-blob-assets-behavior/86942>\
**Category:** Product Support\
**Created:** [May 7, 2018, 7:17pm UTC](https://meta.discourse.org/t/understanding-theme-blob-assets-behavior/86942 "2018-05-07T19:17:14Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![sarahann](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sarahann/32/96703_2.png) [@sarahann](https://meta.discourse.org/u/sarahann)\
**Post date:** [May 17, 2018, 12:02am UTC](https://meta.discourse.org/t/understanding-theme-blob-assets-behavior/86942/5 "2018-05-17T00:02:14Z")

</div>

So I dug a little deeper into why we were having an issue with our uploaded assets.

We have a development environment of Discourse, and the assets live on a development blob storage. When we were making our production environment, we backed up dev and restored it to our production environment. This way, we could have all of our settings and some forum posts.

But it looks like the uploads table gets brought over as well.  
So now we have a production instance, with our uploads table filled with links that point to our development blob storage.

I can’t upload the images into production, because the hashes exist in the uploads table and the url’s will not be updated.

Any ideas on how to get around this in the future? I feel like I am missing something.

---

_[View the full topic](https://meta.discourse.org/t/understanding-theme-blob-assets-behavior/86942)._