# Problem updating data in the separate database

**URL:** https://meta.discourse.org/t/problem-updating-data-in-the-separate-database/317847
**Category:** Self-hosting
**Created:** [July 23, 2024, 2:17pm UTC](https://meta.discourse.org/t/problem-updating-data-in-the-separate-database/317847 "2024-07-23T14:17:33Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [July 23, 2024, 3:47pm UTC](https://meta.discourse.org/t/problem-updating-data-in-the-separate-database/317847/5 "2024-07-23T15:47:51Z")

</div>

My guess is that you’re trying to launch some image that you didn’t build with `launcher`? You might be able to do something like

```
   rake db:migrate

```

after the new image has launched. (There’s a more-complicated more-correct way to postpone some migrations until the new image has launched and the old one has shut down. See `SKIP_POST_DEPLOYMENT_MIGRATIONS` and the `db:ensure_post_migrations` rake task).

Oh, and you’ll need to have all of your assets on S3 as described in [Configure an S3 compatible object storage provider for uploads](https://meta.discourse.org/t/configure-an-s3-compatible-object-storage-provider-for-uploads/148916).

---

_[View the full topic](https://meta.discourse.org/t/problem-updating-data-in-the-separate-database/317847)._