You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've ported the self-hosting stack to Amazon Linux 2023 and adapted http-host for a stateless AWS ALB + Auto Scaling Group deployment (24 commits on my AL2023 branch). Highlights:
AL2023/python3.11 port
TLS removed to serve plain HTTP:80 behind an ALB with --domain
CORS OPTIONS handling
a /healthz/ probe
resilient/resumable huge-download handling
ephemeral-NVMe download staging with extraction onto EBS
--copy-runs-from-host seeding and per-instance local_versions
AMI "bake" workflow in the docs.
Is this upstream project interested in any of this? Would you prefer this as one PR, split into smaller ones (port / ALB / scaling / docs), or behind a flag since the TLS removal is obviously opinionated and will work only in such a set-up where TLS/SSL offloading happens not in NGINX?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi there,
I've ported the self-hosting stack to Amazon Linux 2023 and adapted http-host for a stateless AWS ALB + Auto Scaling Group deployment (24 commits on my AL2023 branch). Highlights:
Is this upstream project interested in any of this? Would you prefer this as one PR, split into smaller ones (port / ALB / scaling / docs), or behind a flag since the TLS removal is obviously opinionated and will work only in such a set-up where TLS/SSL offloading happens not in NGINX?
Cheers,
-- Axel
@hyperknot
All reactions