Skip to content
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

Self-signed certificates #33

Open
reesericci opened this issue Jun 14, 2024 · 4 comments
Open

Self-signed certificates #33

reesericci opened this issue Jun 14, 2024 · 4 comments

Comments

@reesericci
Copy link

reesericci commented Jun 14, 2024

I think it would be nice if thruster allowed for secure local usage easily via self signed certs. I force HTTPS in my rails app, and so I'm going to need to either support HTTP and not know when to redirect to HTTPS or build out some system for self-signed certs and disable HTTP altogether.

Blocked by #40

@reesericci
Copy link
Author

From an implementation perspective, I think having an TLS_SELF_SIGNED env variable makes sense and just storing the CA where the LE certs are.

@reesericci
Copy link
Author

I think I'm going to work on implementing this and see how far I get

@MattKitmanLabs
Copy link

We use a Kubernetes cluster with its own cert manager, I'm wondering if this can run without the need for it to try step in and handle any TLS for us?

@reesericci
Copy link
Author

The main thing is that my PR makes thruster handle its own CA so I don't think this is fit for that use case atm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants