Closed flakey5 closed 10 months ago
~Is there a context to the "fix"? Is the html structure expected for parsing reasons?~
Never mind, just saw the linked issue.
nginx uses columns with fixed length: 50 chars for the file name 1 space date 20 chars for the file size
The name is truncated if it's too long: direct.nodejs.org/download/test The size is written in bytes, without a unit
I'm not sure we should limit to 50 characters, I don't think this is an issue for us.
@flakey5 can you also add an screenshot on some directory listings how it'd look like?
@flakey5 can you also add an screenshot on some directory listings how it'd look like?
I wasn't able to figure out how exactly we should do the spacing. We could do something similar to what nginx does re @targos 's comment, it should work
We can try it. Also would love if dark theme kept working.
This should be good to go, the only difference between the nginx listing & the worker should be that directories don't have a value for the last modified part
Also would love if dark theme kept working.
Same but will probably need to be something we revisit
How we deploy to staging? 🤔
Isn't it done automatically when the PR is merged on main
? I see deploy workflow runs on each commit here: https://github.com/nodejs/release-cloudflare-worker/commits/main/
Isn't it done automatically when the PR is merged on
main
? I see deploy workflow runs on each commit here:main
(commits)
Oh yes, it is :)
Should I merge to test in staging?
There still appears to be some differences
There still appears to be some differences
Ugh, it should give v20.0.9.0... I wonder what is different.
Quotes? (Single vs double)
Quotes? (Single vs double)
Yeah that appears to be the issue, thanks for catching! https://github.com/nodejs/release-cloudflare-worker/pull/76
This PR adopts similar directory listing structure as NGINX to keep existing crawlers and scripts working.