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

luci-app-tinyproxy: change the Bind type to list #7223

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

sasha0552
Copy link

  • This PR is not from my main or master branch 💩, but a separate branch ✅
  • Each commit has a valid ✒️ Signed-off-by: <[email protected]> row (via git commit --signoff)
  • Each commit and PR title has a valid 📝 <package name>: title first line subject for packages
  • Incremented 🆙 any PKG_VERSION in the Makefile (package does not have one?)
  • Tested on: (x86, 64, openwrt-23.05.4, Firefox 124) ✅
  • Mention: @sbyx, @jow-
  • Screenshot or mp4 of changes: image
  • Depends on: tinyproxy: change the Bind type to list packages#24713
  • Description: tinyproxy supports several Bind options, that can be used to create a proxy that (1) supports both IPv4 and IPv6 and (2) uses specific addresses (in my case VPN addresses. It is very important to bind to specific addresses to avoid traffic leaks).

@dannil
Copy link
Contributor

dannil commented Oct 18, 2024

The app was converted to JavaScript with bbb0819 so once the PR in packages gets accepted you would need to rebase and re-implement it in JavaScript, should be trivial tho.

o = s:taboption("general", Value, "Bind", translate("Bind address"),
translate("Specifies the address Tinyproxy binds to for outbound forwarded requests"))
o = s:taboption("general", DynamicList, "Bind", translate("Bind address"),
translate("Specifies the addresses Tinyproxy binds to for outbound forwarded requests"))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we can leave the singular address to keep the old translations not changed. This is probably anyway covers 99% usage scenarious

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

would be great if we could somehow automatically update the translations with small change like this, or even better "queue" a new translation and keep the old one until it is translated. Not sure if this can be done somehow?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you can make sed on po files to change old key to a new to keep existing translation but this may end up with a merge conflict with translations from the Weblate. This is known problem with own issue ticket. So for a such small change I would rather recommend just not to change the translation key.

@stokito
Copy link
Contributor

stokito commented Mar 7, 2025

@Ramon00 maybe you can take finish the PR?

@Ramon00
Copy link
Contributor

Ramon00 commented Mar 7, 2025

I can make new PR I guess, but the underlaying app did not get updated yet. So we cant merge this right now anyway.

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 this pull request may close these issues.

4 participants