Open 34code opened 8 months ago
Hi @34code, unfortunately this isn't straightforward right now, because applications deployed with Kamal are served through another proxy (using Traefik). That proxy terminates the connection, and forwards plain HTTP traffic into the container where Thruster is running. In that configuration, Thruster doesn't have a way to handle the HTTPS traffic.
We're working on some ways to make this simpler on the Kamal side.
But in the meantime, one option would be to have Traefik handle the SSL termination. There's a discussion here that might have what you need to do that.
You can still run Thruster in that setup if its other features are useful to you (like the caching, X-Sendfile, etc).
Thanks for pointing me to that discussion!
I just deployed Thruster with Kamal. Simply keep SSL with Traefik like https://nts.strzibny.name/deploying-rails-single-server-kamal/ and use Thruster for assets (no config there). That's the best/cleanest way right now.
https://nts.strzibny.name/running-thruster-rails-kamal/
I used this one above ^^ and the previous guidance to do SSL with letsencrypt and traefik
Would be cool if thruster supported ssl with letsencrypt directly someday.. as that would be one less network hop from traefik to thruster..
Can live with current setup until then 😀
Turns out it does (thruster ssl support) and I just didn't read about it.. wonder how it plays with default kamal which has zero downtime deploys with traefik
Yes, it does support that, but it's designed for standalone use (like in ONCE products) not with Kamal in mind. I believe this will be somehow solved in Kamal 2 with a new proxy or update to Thruster.
Thanks for building this!
I could definitely use SSL support.. Just wanted to understand how to use with kamal for deployment? I'm trying to simply copy a ubuntu generated
thrust
into my dockerfile via./bin/rails
directory.Doesn't seem to work.