Closed mitra42 closed 4 years ago
Note this is in parallel to any work done in dweb-transports to split it up and re-modularize it.
.____padding_file/123
download handles this fineArchive.js / AdvancedSearch < /arc/archive.org/advancedsearch
ContentHash
/arc/archive.org/metadata and ArchiveItem.metadata
Python/ServerGateway
Done: DAC; IAUX DA, DM, dweb-torrent, dweb-metadata for dweb.me dweb.archive.org upstreamPrefix gatewayServer httpUrl
Note DA.SettingsComponent and DA.LocalComponent go to mirror correctly
All these below moved to ROUND 4 below
STR
Uncaught (in promise) DOMException: Failed to load because no supported source was found.
Diagnosis
This appears to be fixed, not sure how but prob in fixing other routing issues.
Files served by dweb.archive.org (inc archive.html, languages, includes etc) see below
Python code is now gone .... both www-dweb.dev.archive.org and dweb.archive.org run on Javascript express servers now.
From kubectl logs -n$NS pod/$POD
It would be better if dweb-mirror wasn't dependent on dweb.me, that could involve a) calling archive.org directly where appropriate, b) a + performing data manipulation on return rather than in dweb.me c) microservices running on dweb.me that dont depend on the core deb.me server
Next comment will be list of places
(Scroll down to "ROUND 4") but all issues now have own topics so closing