# Migrating assets from old installation into docker

**URL:** <https://meta.discourse.org/t/migrating-assets-from-old-installation-into-docker/36799>\
**Category:** Self-hosting\
**Created:** [12월 16, 2015, 7:08오후 UTC](https://meta.discourse.org/t/migrating-assets-from-old-installation-into-docker/36799 "2015-12-16T19:08:29Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![stefanini.mf](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stefanini.mf/32/121693_2.png) [@stefanini.mf](https://meta.discourse.org/u/stefanini.mf)\
**Post date:** [12월 16, 2015, 11:39오후 UTC](https://meta.discourse.org/t/migrating-assets-from-old-installation-into-docker/36799/3 "2015-12-16T23:39:07Z")

</div>

Thanks for the reply 😃

> [@sam](#):
>
> Wait, why not simply use the backup/restore option?

If I understood it correctly, the backup/restore option would also include a dump of the whole database, right?  
If that’s the case, I’d be backing up a rather big DB (2m posts and 300k users), then restoring it on itself (as both instances currently use the same RDS). That’s a overhead that I’d like to avoid if I could.

> [@sam](#):
>
> Search that area on the host.

Oh. `/uploads` inside that directory seems to be exactly what I’m looking for. 😃 As far as I understood these folders’ content will be mounted inside my docker, right? Then that should even work for logo and favicon images as well, I guess.

That’s really good! I’ll check if it works.

😃

---

_[View the full topic](https://meta.discourse.org/t/migrating-assets-from-old-installation-into-docker/36799)._