Restructure FAQ section
Nobody has claimed this yet.
- Dominant language
- Nix
- Stars
- 4k
- Forks
- 339
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 7
Description
Problem statement
Currently the FAQ sections on nix.dev and the NixOS Wiki are an unstructured collection of question-answer pairs. Some of them are for troubleshooting, some of them are actual recipes for performing common tasks, some are conceptual in nature.
Objective
Since many answers are not as helpful as they could be, we will sort through all questions, and for each make a PR that updates the answer and adds it to the appropriate category on nix.dev.
Tasks
- Check each question on NixOS Wiki: FAQ
- Make a PR for each question on nix.dev below
Troubleshooting
- What to do if a binary cache is down or unreachable?
- How do I fix: error: querying path in database: database disk image is malformed
- How do I fix: error: current Nix store schema is version 10, but I only support 7
- I’m getting: writing to file: Connection reset by peer
Recipes
- How do I add a new binary cache?
- How do I force Nix to re-check whether something exists at a binary cache?
- How to operate between Nix paths and strings?
- How to build reverse dependencies of a package?
- How can I manage dotfiles in $HOME with Nix?
- What’s the recommended process for building custom packages? = "How to build a custom package?" – doesn't have a proper response
Concepts
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the NixOS Wiki FAQ and the listed FAQ sections on nix.dev. Check each question, determine whether it belongs under Troubleshooting, Recipes, or Concepts, and update its answer through a separate PR; done means every listed question has been reviewed and appropriately categorized.
Written by the indexing model from the issue text.
Assessment
- Domain
- content, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100