mirch/soupdev

Support your favorite developers :)

soupdev

Support your favorite developers :)

soupdev's Issues

Restructure TF modules and Rust packages

Restructure TF modules and Rust libraries/binaries and split them by functionality.
E.g.:

• payments
• profiles

Create a landing page

Create a landing page and link it to the root of the website.

Payments

• Create Stripe test configuration
• Create a new Lambda + endpoint for managing payments
• Integrate with Stripe
• Log all transactions in a new table

Split the CI/CD process

Currently, any change in the code results in:

• all the linters running
• the Rust code being compiled
• terraform plan or terraform apply being applied on all modules

This should be optimized so only the necessary modules are checked/deployed. E.g.: cargo clippy should not be run when only JS changes have been made.

Create Route53 and Cloudfront resources

Create the resources so soup.dev redirects to the S3 bucket

Redesign the profile page

The profile page needs to be redesigned, because it looks like shit.

First release

This epic contains all the features that are necessary for the first release of the project. The goal of the first release is to demo a fully functioning profile page, with working donations.

Tasks

• #66
• #67
• #68
• #69
• #70
• #72

CI/CD

• Trigger CI for all PRs (lints, TF plan, etc.)
• Trigger CD for all commits to main (deploy frontend to S3, deploy lambda functions, tables, etc.)

Implement TF modules

• Deploy the code as modules
• Have a python script controlling the deployment per module

Profile feature

• Create Users table
• Create GetProfile lambda function + API GW route ( in TF )
• Create "view profile" page

Link the Route53 nameservers to the domain

Create account/login

• Create Cognito resources
• Create new Lambda for registering
• Create new Lambda for logging in
• Add Github integration

Create a README file and documentation

Before going public, the project should be well documented.

Create diagrams for the current architecture and explain them in the README file.
Create separate docs for more in-depth explanations.

Store secrets in SSM

Some secrets are still in plain text, such as the Stripe key. Store these parameters in SSM, and send them to the Lambda functions as env variables. Delete the plain text keys from their respective platforms.