-
-
Notifications
You must be signed in to change notification settings - Fork 121
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
feat: deploy / aws lambda / sst v3 waku stack #912
feat: deploy / aws lambda / sst v3 waku stack #912
Conversation
Co-authored-by: Daishi Kato <dai-shi@users.noreply.github.com>
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Skipped Deployment
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. |
@rmarscher this is based as suggested on the sst tanstack-start stack |
c5ff9f3
to
ed29afb
Compare
Thank you for creating this! I hope it helps it get added upstream to SST. 🙏 |
This is a first draft for a sst stack for WAKU.
Based on the fact, that there can be more than 25 folders (AWS Cloudfront routing limit) on the first level of the public folder only the folder
public/images
andpublic/assets
are copied to s3 and forward by CloudFront.A possible, but more complex solution could handle this by adding a Cloudfunction to Cloudfront which knows all routes and can forward all existing static root level routes.