Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

upgrade whitenoise #541

Open
eevelweezel opened this issue Nov 3, 2024 · 2 comments
Open

upgrade whitenoise #541

eevelweezel opened this issue Nov 3, 2024 · 2 comments
Assignees

Comments

@eevelweezel
Copy link
Contributor

Probably should be addressed concurrently w/ upgrading Django.

@elmq0022 elmq0022 self-assigned this Nov 3, 2024
@elmq0022
Copy link
Contributor

elmq0022 commented Dec 5, 2024

I updated this but need to review the settings for whitenoise per the whitenoise docs and heroku.

@elmq0022
Copy link
Contributor

So I'm actually thinking that we ditch whitenoise altogether and use aws cloudfront / cdn to serve or staticfiles. We already have an s3 bucket setup for images. pricing on cloudfront seems to be negligible up to the first 1TB of data for the month if I read the pricing structure correctly.

I've already done this with my personal site on heroku and it was quite straight forward. All we need installed is django-storages and boto3 (already installed) along with a cloudfront instance associated with our S3 bucket.

At @eevelweezel or @JoeJasinski let me know if you'd like to pair on this in the near future so we can get all the AWS stuff setup ... or I could just upgrade whitenoise 😆

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants