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

Cost savings: Host static in s3 bucket #408

Open
3 tasks
Aveline-art opened this issue Jun 3, 2023 · 1 comment
Open
3 tasks

Cost savings: Host static in s3 bucket #408

Aveline-art opened this issue Jun 3, 2023 · 1 comment
Labels
feature: Architecture Pertains to project architecture and settings PBV: dev all issues for engineering roles (devops, backend, frontend, db) role: devops Pertains to cd/ci tasks size: 3pt Can be done in 31-48 hours

Comments

@Aveline-art
Copy link
Member

Aveline-art commented Jun 3, 2023

Overview

As a developer, we should keep our product scalable and cost effective. For this ticket, we will try to save on hosting costs by hosting our static in s3.

Action Items

  • Find a way to upload webpack bundled static onto s3 in staging and production (dev should continue to serve static locally)
  • Also find a way to upload django collectstatic onto s3 in staging and production
  • Configure django in staging and production to look for static from an s3 bucket

Resources/Instructions

Resources

This is a good ticket to have in our back pocket when we need to cut costs. Since the frontend and backend directory is mostly independent of one another, we can further reduce our reliance on connecting them by serving our static via s3 rather than keeping them in our servers. This will reduce costs since hosting on s3 is dirt cheap.

@Aveline-art Aveline-art added role: devops Pertains to cd/ci tasks size: 3pt Can be done in 31-48 hours feature: Architecture Pertains to project architecture and settings ready for milestone labels Jun 3, 2023
@alexlaw528 alexlaw528 self-assigned this Oct 14, 2023
@ghost
Copy link

ghost commented Nov 7, 2023

@alexlaw528 Can you please give provide an update for this issue by answering the following:

Progress:
Blockers

Availability:
ETA:

@ExperimentsInHonesty ExperimentsInHonesty added the PBV: dev all issues for engineering roles (devops, backend, frontend, db) label Jun 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature: Architecture Pertains to project architecture and settings PBV: dev all issues for engineering roles (devops, backend, frontend, db) role: devops Pertains to cd/ci tasks size: 3pt Can be done in 31-48 hours
Projects
Status: 📋 Prioritized Backlog
Development

No branches or pull requests

5 participants