c2f7f47eba88691d38761245a855b796b2d07852
The saved settings win over the first-run constants, so a typed URL that never survived a successful transport kept losing to the old PHP endpoint. The device's settings.bin was removed (the vault cache was NOT - it is the only offline copy on that phone, and wiping it is not needed to change an address). The Android constant now points at the contents API rather than the repo URL: it is the one that returns the file with its sha, and the client recognises "/api/v1/repos/" to pick that transport. Windows keeps the local endpoint - the machine hosts it, and nothing requires it to go out on the network to read itself. The token stays out of the repository, as does the sync password: both live in the gitignored PMA.LocalConfig.inc, or get typed on the device. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Description
full local password manager
Languages
Pascal
46.7%
JavaScript
35.4%
HTML
9.4%
CSS
4.9%
PHP
2.1%
Other
1.4%