<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/">
  <channel>
    <title>attachments</title>
    <description>These are all contents from XFROCKS tagged attachments.</description>
    <pubDate>Tue, 24 May 2016 11:44:16 +0000</pubDate>
    <lastBuildDate>Sat, 25 Apr 2026 18:14:01 +0000</lastBuildDate>
    <generator>XFROCKS</generator>
    <link>https://xfrocks.com/tags/attachments/</link>
    <atom:link rel="self" type="application/rss+xml" href="https://xfrocks.com/tags/attachments/index.rss"/>
    <item>
      <title>Attachment Store S3 100GB+</title>
      <pubDate>Thu, 02 Jun 2016 10:47:11 +0000</pubDate>
      <link>https://xfrocks.com/other/threads/attachment-store-s3-100gb.489/</link>
      <guid>https://xfrocks.com/other/threads/attachment-store-s3-100gb.489/</guid>
      <author>nokian125</author>
      <dc:creator>nokian125</dc:creator>
      <content:encoded><![CDATA[We moved all the data to S3 manually using AWS cli and now activated this plugin but we found out that this plugin require some extra meta info about each attachment file.<br />
<br />
Can you please let us know what&#039;s the best possible solution for us to move our existing data to S3 that this plugin accepts? Using Move Attachments option in rebuild tool not sounds like a great idea for us so far.]]></content:encoded>
      <slash:comments>7</slash:comments>
    </item>
  </channel>
</rss>
