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.

Sign up for GitHub

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

Jump to bottom

Traefik support #5

Open
decentral1se opened this issue Oct 30, 2021 · 5 comments
Open

Traefik support #5

decentral1se opened this issue Oct 30, 2021 · 5 comments

Comments

@decentral1se
Copy link

Hi folks 👋 We're working on a Co-op Cloud recipe for Snikket and as discussed previously on the dev chat, we're using Traefik as our proxy. We've discussed a bit how to handle this but in the end it seems to be easier to keep up with the developments of this repo if we can just somehow disable automatic lets-encrypt functionality here. Would that be something you'd consider making optional / pluggable? It seems to just require some conditional env var to happen in and around the entrypoint to turn it off.
@decentral1se decentral1se mentioned this issue Oct 30, 2021
Closed
@decentral1se
Copy link
Author

decentral1se commented Oct 30, 2021 •
edited
Loading

I'm opening up #6 just to show you what we're working with now to "turn off" the automagic letsencrypt functionality. We'll pipe env vars into https://github.com/snikket-im/snikket-web-proxy/blob/main/render-template.sh via the environment: ... stanza in our compose configs. Might be handy just to see what change set we're working with.

@decentral1se
Copy link
Author

I'm trying to track back and clear up what is required here, and I think it is "just" this change: 3-w-c@bcec18a. The change is explained in the 5th point of #6 (comment). If anyone can see a way forward here, I'll happily try to implement something. I'd love to get back on the mainline images for snikket.

@decentral1se decentral1se changed the title snikket-web-proxy without automagic letsencrypt? Traefik support Jan 9, 2022
@decentral1se decentral1se mentioned this issue Jan 9, 2022
Open
mwild1 added a commit that referenced this issue Oct 24, 2023
@mwild1
Allow customizing which protocols get enabled (#5)
3786198 
This allows customization of which "protocol" templates get rendered. Alone,
it's not very useful. However, a subsequent image layer could add additional
templates and enable a custom set using this variable.
@mwild1
Copy link
Member

mwild1 commented Oct 24, 2023 •
edited
Loading

I'm working on a new release, and I've merged what seems generally applicable from the commit referenced above. Rather than patching the image, the appropriate approach now would be to add e.g. a httponly template with the desired changes (by adding a volume or a new image layer), and then set SNIKKET_TWEAK_WEB_PROXY_PROTOS=httponly and SNIKKET_TWEAK_WEB_PROXY_RELOAD_INTERVAL=inf.

I hope this is useful!

@damufo
Copy link

damufo commented Feb 21, 2024 •
edited
Loading

Very thanks to developer snikket-im.
Please add support for traefik and add example in https://snikket.org/service/help/advanced/reverse_proxy/

@Sythelux
Copy link

What is the state of this? Can it be tested? I can provide feedback.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@mwild1 @Sythelux @decentral1se @damufo