Configured s3, but i want asset to serve locally

[hosna]

I have already configured s3 according to this guide:

Configure an S3 compatible object storage provider for uploads

This topic covers how to configure some common S3 compatible Object Storage providers (S3 clones). See Set up file and image uploads to S3 for more details about Amazon AWS S3 configuration, which is officially supported and used internally by Discourse for our hosting services. Provider Service Name Works with Discourse? Amazon AWS S3 Yes Digital Ocean Spaces Yes Linode Object Storage Yes Google Cloud Storage Yes Scaleway Object Storage Yes Vultr Obj…

what should i do if i want discourse assets to still serve locally?

[Don]

Hello The title and content of the topic are a bit contradictory but I assume you want to store assets on Object Storage.

@Discourse

In order to store Discourse static assets in your Object Storage add this configuration on your app.yml under the hooks section:

  after_assets_precompile:
    - exec:
        cd: $home
        cmd:
          - sudo -E -u discourse bundle exec rake s3:upload_assets
          - sudo -E -u discourse bundle exec rake s3:expire_missing_assets

[hosna]

Sorry about that. You are right. I just edited the post. I want assets to be served locally

[hosna]

my problem is that when I enable after_assets_precompile the rebuild hangs In rake s3:upload_assets line for one hour, so I terminated the process. and also when I disable after_assets_precompile, my forum wont show up due to not finding assets on s3.

[pfaffman (Jay Pfaffman)]

@hosna

my problem is that when I enable after_assets_precompile the rebuild hangs In rake s3:upload_assets line for one hour

I believe that is the problem you want to solve. It’s a good bet that this is a symptom of your problem, not the problem itself.

I think if you set DISCOURSE_USE_S3 to false (or maybe just don’t include it), it won’t push the assets to s3.