-
Notifications
You must be signed in to change notification settings - Fork 0
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!: Drop WASM target, add Docker #50
Conversation
37df2b9
to
a4519a6
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files📢 Thoughts on this report? Let us know! |
d469b7e
to
108c7ed
Compare
781c8dc
to
508367d
Compare
508367d
to
b290b0a
Compare
b290b0a
to
a5338f7
Compare
6c26ce5
to
5ef3ecf
Compare
Instead of Google Cloud Run, Azure Container Apps might make sense. https://azure.microsoft.com/en-us/products/container-apps#Pricing Google free tier:
Azure free tier:
Main benefit is that Azure allows providing an origin certificate so I can keep cloudflare in front for DDOS mitigation and CDN cache (once needed) where google can do custom domain mapping, requiring the use of the google cert or adding a load balancer in front, which does not have a free tier. |
This removes WASM (and as a result cloudflare) as the deployment target. Instead this builds a docker container to deploy anywhere. Tokio now takes care of the async runtime, flushing of OTLP is handled by a background task, every second, instead of every request. The list-package endpoint's `href`'s will now use relative paths, not sure how I missed this was an option. The `href`'s also no longer urlencode "https://" This prevents issues when running behind proxies that url-decode requests before hitting our server. The url encoding stays in place so we can locally use http instead of https. It can still happen that some registries are incorrectly decoded and passed on to our server, potential problem for future me.
This removes WASM (and as a result cloudflare) as the deployment target. Instead this builds a docker container to deploy anywhere.
Tokio now takes care of the async runtime, flushing of OTLP is handled by a background task, every second, instead of every request.
The list-package endpoint's
href
's will now use relative paths, not sure how I missed this was an option.