External/5chan
1
0
Fork 0
mirror of https://github.com/bitsocialnet/5chan.git synced 2026-08-03 07:41:04 +02:00
Code Issues Packages Projects Releases Wiki Activity

fix(portless): force HTTPS proxy startup

Browse Source
This commit is contained in:
Tommaso Casaburi
2026-04-28 14:34:23 +07:00
parent 34b60c7d53
commit 33bf4dabce
2 changed files with 31 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/agent-playbooks/known-surprises.md
+10
View File
@@ -28,6 +28,16 @@ If uncertain, ask the developer before adding an entry.
## Entries
### Portless 0.11 reuses legacy proxy state unless the launcher forces HTTPS
- **Date:** 2026-04-28
- **Observed by:** Tommaso + Codex
- **Context:** Upgrading the normal `yarn start` flow from the old `http://5chan.localhost:1355` proxy URL to `https://5chan.localhost`.
- **What was surprising:** Even with `portless@0.11.1` installed, Portless reused the existing `~/.portless/proxy.port = 1355` HTTP proxy and printed the legacy `:1355` URL.
- **Impact:** Updating package versions and docs is not enough; `yarn start` can still advertise and use the old URL when a contributor has legacy Portless state running.
- **Mitigation:** Keep `scripts/start-dev.js` explicitly starting the Portless HTTPS proxy on port `443` before registering the app route, so the runtime flow migrates away from persisted `1355` state instead of inheriting it.
- **Status:** confirmed
### Android release signing still uses legacy keystore names
- **Date:** 2026-04-23