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
We should support HTTPS, to do so we should change the nginx config and write a guide to let users deploy their certificate on nginx.
I know this tools https://github.com/FiloSottile/mkcert that should simplify certificate creation, but I'm open to other suggestions. The procedure should be easy to follow and detailed on buffalogs readme.
The text was updated successfully, but these errors were encountered:
We can update the Nginx configuration to support HTTPS. Instead of using mkcert, I plan to implement this using AWS services, likely AWS Certificate Manager (ACM) and an Application Load Balancer (ALB) to handle SSL termination. This way, we can automate certificate management and make the setup more scalable.
Understood! Try Certbot—it provides free SSL certificates from Let's Encrypt and automates renewals. This keeps the project self-hosted and deployable anywhere without relying on a cloud provider
@ManofWax I feel like this SSL support use case should be more of the responsibility of the user, as there are multiple ways to convert http to https by changing the config files and then attaching the ssl cert. Some may prefer Let's encrypt, some mkcert and some their own ones.
Also , security teams using them would use Buffalogs in an air gap environment and maybe fine with it being run on http. This is Issue won't be that high priority is I suppose ? :)
Nginx configuration only supports HTTP right now.
We should support HTTPS, to do so we should change the nginx config and write a guide to let users deploy their certificate on nginx.
I know this tools https://github.com/FiloSottile/mkcert that should simplify certificate creation, but I'm open to other suggestions. The procedure should be easy to follow and detailed on buffalogs readme.
The text was updated successfully, but these errors were encountered: