ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Castopod Amazon S3 Configuration / Backblaze B2

    Scheduled Pinned Locked Moved IT Discussion
    castopod
    4 Posts 3 Posters 624 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • scottalanmillerS
      scottalanmiller
      last edited by

      If you want to use Castopod, you almost certainly want to connect it to an S3 bucket. But the documentation on the site is missing a couple critical elements. The bucket must be specified and the format of the host needs the header. Here is an example configuration from the end of the .env file.

      media.fileManager="s3"
      media.s3.endpoint="https://s3.us-east-001.backblazeb2.com"
      media.s3.bucket="bucketname"
      media.s3.key="mykeyID"
      media.s3.secret="mykeySecret"
      media.s3.region="us-east-001"
      

      This took some tracking down. The media.s3.bucket is absolutely critical, but does not appear in the documentation. The https:// I'm told is required as it prefixes bad data without it.

      1 Reply Last reply Reply Quote 1
      • travisdh1T
        travisdh1
        last edited by

        That looks like a real pain to have tracked down!

        1 Reply Last reply Reply Quote 0
        • A
          anyaburke
          last edited by

          You need to specify the AWS access key, secret access key, default region, S3 bucket name, and the AWS endpoint URL.
          The AWS endpoint URL should be in the format "https://s3.your-region.amazonaws.com" age of war

          1 Reply Last reply Reply Quote 0
          • A
            anyaburke
            last edited by

            The host format should start with "https://s3." followed by the AWS region and ".amazonaws.com".
            The full format is: https://s3.your-region.amazonaws.com
            Replace your-region with the actual AWS region where your S3 bucket is located.

            1 Reply Last reply Reply Quote 0
            • 1 / 1
            • First post
              Last post