# 迁移到 S3 以解决 Digital Ocean Spaces 的问题

**URL:** <https://meta.discourse.org/t/migrate-to-s3-for-digital-ocean-spaces-woes/109662>\
**Category:** Self-hosting\
**Tags:** s3\
**Created:** [2019年二月20日 15:54 UTC](https://meta.discourse.org/t/migrate-to-s3-for-digital-ocean-spaces-woes/109662 "2019-02-20T15:54:27Z")\
**Posts on this page:** 1\
**Showing post:** 12

<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:** [2019年二月27日 21:43 UTC](https://meta.discourse.org/t/migrate-to-s3-for-digital-ocean-spaces-woes/109662/12 "2019-02-27T21:43:31Z")

</div>

> [@gerhard](#):
>
> It must be the `url` column in the `topic_links` table. It’s the only column with a restriction of 500 chars.

Thanks for that. I’ve got 30 on this site (different from the site discussed [here](https://meta.discourse.org/t/trouble-with-discourse-remap-remapping-topic-links-url/110052)) with more than 490 characters. I’m not clear why the remap has this problem. Oh! Is it because this table is getting populated when the posts are rebaked? If that’s it, isn’t it a bug if sticking a URL with \>500 characters in a post causes this error? Should there be some error checking that catches it?

> [@Trouble with \`discourse remap\` remapping \`topic\_links url\`](https://meta.discourse.org/t/trouble-with-discourse-remap-remapping-topic-links-url/110052):
>
> I’m trying to discourse remap community.x.com staging.community.x.com as described [here](https://meta.discourse.org/t/replace-a-string-in-all-posts/48729) (edit: Hmm. Maybe I should have made this a post over there?) and am getting this error: Remapping topic\_links url Error: ERROR: value too long for type character varying(500) The remap has only been partially applied due to the error above. Please re-run the script again.

Tagging @falco since he was involved in the other topic about this.

---

_[View the full topic](https://meta.discourse.org/t/migrate-to-s3-for-digital-ocean-spaces-woes/109662)._