docs.lix.systems leads you to a false URL that fails to render #434
Labels
No labels
Area/build-packaging
Area/cli
Area/evaluator
Area/flakes
Area/language
Area/profiles
Area/protocol
Area/releng
Area/remote-builds
Area/repl
Area/store
bug
Cross Compilation
devx
docs
Downstream Dependents
E/easy
E/hard
E/help wanted
E/reproducible
E/requires rearchitecture
imported
Needs Langver
OS/Linux
OS/macOS
performance
regression
release-blocker
RFD
stability
Status
blocked
Status
invalid
Status
postponed
Status
wontfix
testing
testing/flakey
ux
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: lix-project/lix#434
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
The docs don't render. Seems reproducible on most systems.
Checklist
[source]
Okay. So when you go to https://docs.lix.systems it directs you to https://docs.lix.systems/manual/nightly but that link is incorrect. And should be https://docs.lix.systems/manual/lix/nightly instead.
docs fail to renderto docs.lix.systems leads you to a false URL that fails to rendersigh I'm the one who wrote it, with Jade's help. currently there is no sort of autodeploy, and the file isn't checked in anywhere (I have a copy, and also there's the live copy). this is bad, but it was a very quick placeholder.
anyway, the way to deploy it right now is to manually use rclone to copy to/from our s3 on garage. the directions for setting up s3 credentials for your rclone are in
lix/maintainers/upload-manual.md
. this is a counterintuitive place to look if you don't already know; even knowing, I almost didn't manage to find it again. after considerable pain I was able to figure out how to use it again. I may see if I can add a wiki page about s3, this knowledge shouldn't live just in a couple people's heads.anyway I fixed it, thanks for filing the report!
there's a bad rewrite rule that does work but it's possible it mishandles / at the end or something. we can possibly look at it today but no promises, and we may forget.