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

Figure out a good processes for NMHC to be able to update PDFs on the Our Research & Resources section #207

Open
m3ssij3ssi opened this issue Jul 5, 2022 · 1 comment

Comments

@m3ssij3ssi
Copy link
Collaborator

m3ssij3ssi commented Jul 5, 2022

Sometimes we get updated PDFs of the files in the "Our Research & Resources" section. It would be great if there was a easier way for NMHC to be able to update this on our own if a file is updated. Let's talk through options. We can do this after July 12th.

@m3ssij3ssi m3ssij3ssi changed the title Figure out a good processes for NMHC to be able to update PDFs on the Resources - Publications Section Figure out a good processes for NMHC to be able to update PDFs on the Our Research & Resources section Jul 5, 2022
@acidjazz
Copy link
Owner

acidjazz commented Jul 14, 2022

After @m3ssij3ssi noticed we have a 30MB limit for files in git - I think it's best we move these PDF's to S3:

  • Setup a public read-only bucket that hosts the PDF files
  • Point all code to this bucket
  • Upload all PDF's in /static/pdf to this bucket and remove them from the source code
  • Generate Private Credentials that have write access to this bucket
  • Build a Wiki page detailing on how to connect to this bucket and transfer files (suggest cyberduck/etc)
  • Figure out a way to keep the credentials private somewhere

CloudFront

  • Point S3 to our cloudfront setup - something like /pdf/
  • Make sure PDF's work as that url - do not go directly to S3
  • Change all links to point to the CloudFront URL

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

No branches or pull requests

2 participants