定义 DISCOURSE_S3_CDN_URL 以链接 S3 CDN URL 中的资源

支持
1

I had this problem before and decided that I was crazy, confused, or the database on the site was suspect, but this is on a brand new site. Also, I was on Digital Ocean spaces, so I thought it might be a problem somehow.

I’m trying again to figure out how to keep images on AWS S3 like I think the Big Boys do.

Here’s what I have in the env section:

  DISCOURSE_S3_ACCESS_KEY_ID: 'key'
  DISCOURSE_S3_SECRET_ACCESS_KEY: 'lock'
  DISCOURSE_BACKUP_LOCATION: 's3'
  DISCOURSE_S3_BUCKET: 'lc-xyz'
  DISCOURSE_S3_BUCKET_NAME: 'lc-xyz'
  DISCOURSE_S3_BACKUP_BUCKET: 'lc-xyz/backups'
  DISCOURSE_S3_UPLOAD_BUCKET: 'lc-xyz/uploads'
  DISCOURSE_S3_CDN_URL: 'https://lc-rbx.s3.amazonaws.com'

When I include the s3 cdn url the site breaks because all of the links to the assets are on S3 like https://lc-xyz.s3.amazonaws.com/assets/plugin-third-party-01ba4719c80b6fe911b091a7c05124b64eeece964e09c058ef8f9805daca546b.br.js.

Because if you define s3 cdn url Discourse looks for the assets on the s3_cdn_url.

I did a rebuild, but the assets are still missing. I can do a

rake s3:upload_assets

Is there an after_bundling_assets stanza that I could add that to? (I know about after_db_migrate and after_bundle_exec, but don’t know if those would work.)

Do assets get produced some other time? (It would seem like when themes get modified assets would change.)

If I also had a “push CDN like normal”, would that keep this from happening?

Is there some best practice that I’m missing?

1 个赞
2

You can use after_assets_precompile as the hook for that rake task.

4 个赞
3

Aha! Thanks very much for that. Where does the list of those things live?

I’m still confused why this is necessary, especially since you seemed confused before. (Or maybe I should be happy that I can push all this stuff to S3, now that I know how to do it–And I think that it was you who said that one could use CloudFlare’s free CDN to front an AWS bucket.)

4

I’m trying this again. I’ve got uploads going to s3. That works.

I configured cloudflare to CDN the site. If I enter https://lc-XXX.literatehosting.com/uploads in the s3_cdn_url site setting, new uploads go to the S3 bucket and the image is linked to the CDN url and it works.

BUT if I try to set the s3_cdn_url with an ENV in app.yml (or edit config/discourse.conf by hand and sv restart unicorn, all of the assets are loaded from S3 (where they aren’t). That might be OK, but if I try to rake s3:upload_assets, it complains that S3 isn’t configured.

1 个赞
5

I happened across this while figuring out some clashing settings names.

I think (and hope, because it means I understand this and didn’t write absolute nonsense in the thread linked above) that if you remove these two lines:

DISCOURSE_S3_BUCKET: 'lc-xyz'
DISCOURSE_S3_BUCKET_NAME: 'lc-xyz'

Then you can set DISCOURSE_S3_CDN_URL, and it will only be used for uploads, not assets.

3 个赞
6

I think that you do understand, and, thanks to you, I’m at least closer to understanding myself! Thanks very much!

1 个赞
7

Running into this and still very confused after reading this thread…

I’m trying to server s3 uploads (not compiled assets) from CDN (Cloudfront).

If I configure “s3 cdn url” via the settings screen, it works as expected (well…except for System upload not using s3 cdn url)

However, if I configure via DISCOURSE_S3_CDN_URL and rebuild, the frontend is broken because its trying to load compiled assets from my s3 cdn url.

Seems DISCOURSE_S3_CDN_URL / s3_cdn_url should only affect uploads, and DISCOURSE_CDN_URL should only affect assets.

2 个赞
8

That is my experience too. I ended up making a plugin to set the S3_CDN_URL.

2 个赞
9

@pfaffman seems like this should be filed as a bug then, yes?

10

Perhaps. It’s not a feature likely to be used by normal self hosters,so it’s going to be a low priority. Also, I think that there is soon to be a change in how global settings and shadowed by global work, so it’ll likely get worked out then.

11

seems the same issue turn me down here
@pfaffman need your help
do you use cloudfront to achieve the custom domain cdn url or just use the public prefix of bucket objects in cdn url

12

我刚刚遇到了这个问题。@pfaffman，你解决这个问题了吗？

我通过手动在站点设置中配置 s3_cdn_url 让上传功能正常工作，但理想情况下，我希望在部署时能全局设置该环境变量。当我这样做时，却遇到了同样的问题：Discourse 试图在 s3_cdn_url 中查找资源，我认为这看起来像是 discourse/lib/content_security_policy/default.rb at main · discourse/discourse · GitHub 中的一个 bug。

13

我想我刚刚已经在数据库中设置了该值。

我的猜测是，解决方案是找到将资源推送到 S3 的 rake 任务。

14

我想请问一下，@team 中的任何一位能否确认这是否是预期行为：即无法在不让 Discourse 也在此处查找资源的情况下，使用 S3 CDN（全局设置）来上传文件。除非我误解了什么，否则这似乎是一种出乎意料的行为。

15

是的，这就是预期行为。

配置 S3 CDN 后，它将用于所有静态文件，无论是上传的文件还是 JS 资源。

1 个赞
16

这里有一些相关信息，我上个月也处理过这个问题。

我的解决方法是同时设置两个变量（DISCOURSE_S3_CDN_URL 和 DISCOURSE_CDN_URL），并创建两个 CloudFront 分发：一个用于上传文件，源站为 S3 存储桶；另一个用于资源文件，源站为服务器。

以下是我们使用的代码：

以下是我们的 app.yml（我们将其命名为 web.yml），我们在构建时替换变量：infra/modules/services/discourse/web.yml at master · debtcollective/infra · GitHub

4 个赞
17

太棒了，非常感谢。这方面似乎几乎没有文档，而且设置暗示你只能使用 S3 进行上传，我想这正是让我们所有人困惑的地方。

2 个赞
18

这已列入我的待办事项，我计划在本周末前写一篇关于此的#操作指南。

6 个赞
19

是的，一旦你明白需要两个 CloudFront 分发，就会觉得更有道理了。另外，请记住在每次重建后将资源上传到 S3。从 Docker Manager 升级时存在一个问题，需要手动在 Docker 容器内运行 bundle exec rake s3:upload_assets。如果你选择重建，只要在 app.yml 中添加以下行，应该就能正常工作：

hooks:
  after_assets_precompile:
    - exec:
        cd: $home
        cmd:
          - 'bundle exec rake s3:upload_assets'
5 个赞
20

该任务报错提示我尚未配置 S3。我已将问题定位到 global_setting.rb 中的这个方法：

def self.use_s3?
    (@use_s3 ||=
      begin
        s3_bucket &&
        s3_region && (
          s3_use_iam_profile || (s3_access_key_id && s3_secret_access_key)
        ) ? :true : :false
      end) == :true
  end

GlobalSetting.s3_bucket 应该在哪里定义？看起来我们需要设置 DISCOURSE_S3_UPLOAD_BUCKET 和 DISCOURSE_S3_BUCKET 这两个环境变量。它们之间有什么区别？