💾 Archived View for station.martinrue.com › smokey › 6ddc214d8e2c41e5ae8193dabf526387 captured on 2023-09-08 at 17:54:31. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2023-07-22)
-=-=-=-=-=-=-
Are there any public ducking proxies or in depth guides to setting one up locally?
1 year ago
I saw that. Nice work @smokey! The only thing I'd add is that you don't *technially* need to use your public-facing IP address for your certificate or connecting to duckling; the loopback address (127.0.0.1) works just fine (at least on Linux). If you're machine is using DHCP and your setup stops working when you get a new address, try changing the Lagrange settings but leaving the certificate alone. · 1 year ago
I managed to get it up and running, will write up my own guide. Thank you @wilburthefirst and @degrowther2 for your replies :) · 1 year ago
I don't know Go, *at all*, but I was able to get it going with no trouble. I think the "trickiest" bit was generating a key, but I had to jump through that hoop recently so I was ready to go with gemcert. I haven't bothered setting it up to run it as a service, I just launch it manually the first time I try to reach a web page from Lagrange. · 1 year ago
I don't have links but I was looking into this this morning. The source code to duckling is a bit outdated and crashed when I tried to use it.
I was playing around with updating to use the latest go-gemini. If I get it working I'll let you know.
I can probably write up a guide, how technical are you (comfortable with the CLI and using something like Go?) · 1 year ago