Ship default tunnel_cache for users blocked from the master list#902
Ship default tunnel_cache for users blocked from the master list#90211EJDE11 wants to merge 2 commits into
Conversation
Updated to include tunnel refresh action on publish release
SadPencil
left a comment
SadPencil
left a comment
There was a problem hiding this comment.
LGTM. Is there a 2nd review?
|
@11EJDE11 This PR was a draft somehow. Is it ready for merge? |
Yeah, I haven't tested it and don't want to mess up the updater if it's wrong. Can we put it in Pre Release? |
yeah. ideally this should be named canary instead of pre-release alternatively any branch starts with feature/ can also be automatically pushed to update server |
|
I've pushed to pre-release, @SadPencil. What happens now? |
You can then ask some Russian players to test by switching to pre-release channel in client option window |
3 participants
Summary
package/Client/tunnel_cache(seeded from the current master list) so users who can't reachhttps://cncnet.org/master-list(e.g. Cloudflare-blocked regions like Russia) have a working tunnel list out of the box.Client/toversionconfig.ini[Include]so the updater tracks and refreshes the seed file on every package update..gitignoreto keep ignoring localClient/state while tracking onlytunnel_cache.Why
The client (
TunnelHandler.cs) already falls back toClient/tunnel_cachewhen the master list URL fails. Until now the only way to deliver that file to affected users was DM'ing it on Discord, which goes stale quickly. Bundling it via the package means blocked users get a refreshed snapshot on each release.For unblocked users this is a no-op: the file is overwritten on the first successful master list fetch.
Maintenance
Refresh the seed file shortly before each release:
curl https://cncnet.org/master-list -o package/Client/tunnel_cache